| cashbox_ab_full_amt_auth | This parameter is used to instruct the system whether to perform a full auth for a new subscription, or only a validation call to check the card account is open. In older SOAP versions, this was the only way to ensure the card provided with the subscriptions was valid. Since then, an option was added to enable the validation of the card for future payments- in case we creat a free trial and we dont charge the customer immediately and we moved to full auth for all the other cases in order to ensure that there are also sufficient funds | The parameter is in use for very old merchants . For new merchants, this is always set to true (1) | |
| cashbox_ab_partial_auth | Defines whether or not to accept partial authorization (and payment) for submitted transactions. (Required.) 0: Does not allow partial authorization. (Default.) 1: Allows partial authorization for transactions. | This is not in use anymore and should not be exposed for configuration | |
| cashbox_rt_capture_delay | This was related to enable a setting to not perfomr the online capture immediateDefault value should be leave empty | This is not used anymore and should not be exposed for configuration. For historic purposes can review CB-15129 | |
| merhcant_no_validaiton | Defines whether CashBox will use its default payment method validation for all transactions, or use special credit card validation calls supported by some payment processors. NULL: CashBox will validate all payment methods by authorizing a transaction for a nominal (0or1) amount. (Default.) 1: CashBox will use special credit card validation cards where applicable, such as Chase Paymentech for some card types. | This should not be used or exposed for configuration. No merchants have this set to 1 | |
| avs_cvn_custom_policy | This was used to enable merchants to set their own policy for avs/cvn vaidation | This is not exposed in Portal1 and it is not set for any merchant. No instruction on how to use this | |
| zero_tx_item_merge | Once upon a time all AutoBills had only a single line item (we did something rather ludicrous like pulling the SKU off of the AutoBill’s Product, but use the BillingPlan description. When we implemented AutoBills with multiple items, resulting Transactions would have multiple line items (1 for the BillingPlan, and 1 for each active AutoBillItem). Many of our Merchants became severely disgustipated because they did not like that Transactions being sent to customers now looked different. To (at least temporarily) resolve this issue we came up with a bunch of goof rules for whether or not to merge TXItems into a single item (messy- very messy). At roughly the same time we were dealing with complaints about wanting Transactions for BillingPeriods where the payment amount was 0. The end result of this great emotional singularity was to create the zero_tx_item_merge. Setting this value to 1 means “Do NOT generate 0-amount Transactions” & “Do merge TXItems if the items meet our cheesy looks-like-pre-Soap-3.7 rules. This is the old way of doing things. Setting this value to 0 means “DO generate 0-amount Transactions” & “Do not even think of merging TXItems so Transactions look like something we did a decade ago). This is the new way of doing things. (default) Note that we have an option on Autobill (zero_tx_no_item_merge) … which is set by all newer Soap versions which takes precedence over this Merchant option. | Today this is not visible in the portal and it is set to default to zero. Newer functionalities added do not handle this feature - like autobill.modify | |
| cashbox_realtime_void | The purpose of this option is to define whether the authorized funds should be released immediately or let the authorization cancel by itself. Not all payment processor support this option. When a transaction is authorized, it can be cancelled before it is captured. For certain payment processors, who charge a fee if you do not capture an authorized transaction, Subscribe also reverses the authorization. For other processors, Subscribe simply deletes its internal to-be-captured flag so that the Transaction is no longer scheduled for capture. | To determine whether Subscribe performs authorization reversal with your payment processor as a part of this call, contact your Vindicia Client Services representative. | |
