XP Cloud:Choice of Payment Configuration for a Payment
- X-Payments Cloud: General information
- Get Started with X-Payments Cloud
- Two-factor User Authentication
- General Settings
- Payment Configurations
- Services
- Users
- User Interface
- Payments
- Payments List
- Payment Statuses
- Search for Payments
- View the Details of a Payment
- Delete a Payment
- Auth and Capture (Capturing Funds)
- Void an Authorization
- Issue a Refund
- Manage High Risk Transactions
- Emulate Transactions
- Clear Cardholder Data
- Tokenization and Re-Use of Saved Cards
- Delayed Payment Feature
- Supported Payment Gateways
- What's New in X-Payments Cloud
Since you can have more than one payment configurations enabled in X-Payments Cloud, you may want to know whether there is a way to find out which of these payment configurations - and, ultimately, which payment processor - will be chosen to process any specific payment, and whether there is a way to influence this choice.
It is worth mentioning that during checkout X-Payments Cloud does not show its payment configurations to buyers as separate payment options. The buyer only gets one option for payment via X-Payments Cloud, and that one option comprises all the payment configurations that have been added and enabled in the X-Payments Cloud admin panel. The choice of the payment processor at checkout is made by X-Payments Cloud itself based on which payment processor will best serve the purpose of processing a specific payment. For example, such things may be taken into account as the currency that was selected to pay for the order, the type of payment card that was specified as a payment instrument for the order (VISA, MasterCard, American Express, etc.), the order total amount, or whether the order was placed using some kind of special feature (like Apple Pay - which is supported by some payment processors and not supported by others).
Say, you have two different payment configurations for your X-Payments Cloud payment option: one for payments in US dollars (USD), and one for payments in Canadian dollars (CAD). The payment form provided to the buyer at checkout is not linked to any specific payment processor; this form is owned by X-Payments Cloud. After the buyer completes this form and places their order, X-Payments Cloud reviews the order information being submitted. In our example, X-Payments Cloud finds out that, according to the order information, the total amount for this order was in Canadian dollars. Because you only have one payment configuration that supports payments in Canadian dollars, this payment configuration (and the respective payment processor) will be chosen by X-Payments Cloud for payment processing in this case.
With credit card types, it is pretty much the same: if you have a payment configuration that supports a certain credit card type and another one that does not, submitting an order payment using a credit card of that type will trigger the use of the payment configuration that supports the credit card type in question.
Order total limits are another way of routing transactions of specific sizes to specific payment gateways. For example, if you have one payment configuration with Order total limits of $0.00-500.00 and another one with Order total limits of $500.00-5000.00, a payment transaction for the amount of $548.00 will be routed to the latter one.
In the case when all the parameters based on which the choice of the payment configuration is made are equal for multiple payment configurations, the choice of the payment configuration by X-Payments Cloud is made based on the priority settings for those payment configurations (in other words, the order in which they go in the Payment Configurations list) from top to bottom). The first payment configuration that matches all the necessary criteria will be used.
Consider the following example. You add two payment configurations: one for PayPal (you add it first) and one for Authorize.Net (you add it second). Both the configurations are identical but for one feature - Apple Pay: your Authorize.Net configuration supports Apple Pay, whereas PayPal does not. Now if a buyer chooses to pay for their order via Apple Pay, X-Payments Cloud will use your Authorize.Net payment configuration because only that payment configuration supports Apple Pay. If, however, the buyer chooses to pay using a credit card, your PayPal payment configuration will be used for the payment because PayPal was the payment configuration added first.
Knowing the principle of how X-Payments Cloud chooses the payment configuration for a payment, you have more control over this process.
See also:
