Overview of SlimPay payment gateway integration
The following table provides a quick reference for the supported features. For details about each feature, see the later sections in this article.
|Supported payment methods||SEPA, Credit Card Reference Transactions (Tokenization)|
|Supported payment operations||Validate Payment Method, Payment, Void Payment, Referenced refund|
|Support 3D Secure 2.0||No|
|Support Delayed Capture||Yes|
|Support Level 2 and Level 3 card data||No|
|Support stored credential transactions||No|
|Support Gateway Options fields||No|
|SlimPay payment gateways endpoint used for Zuora gateway integration service||
|Support Gateway Reconciliation||Yes|
|SlimPay production endpoint used for Gateway Reconciliation service||
|Support Payment Method Updater||No|
Supported payment methods
The SlimPay payment gateway integration supports the following payment methods:
- Credit Card Reference Transactions (Tokenization)
For more information about setting up payment methods in Zuora, see Define and set up payment methods.
Support for mandate creation
Among the supported payment methods, Zuora supports mandate creation for SEPA payment methods. Zuora will generate and pass the mandate to the gateway.
Credit Card Reference Transactions
Zuora supports SlimPay tokens. Tokens are used for credit card reference transactions in Zuora. A reference transaction is simply a representation of a credit card payment method without having sensitive payment method information like the credit card number stored in Zuora. Please note that the token cannot be used with another gateway, which is why we recommend storing credit card information in Zuora whenever possible.
Zuora’s SlimPay integration supports Card Aliases via the Credit Card Reference Transaction payment method. This feature allows you to leverage the SlimPay’s card-alias API to create credit card payments against subscriptions.
The following table shows the field mapping between Zuora and SlimPay for Credit Card Reference Transaction payment methods.
|Zuora REST API or SOAP API||SlimPay API|
When creating a payment method from the Zuora UI or API, you need to populate the token generated from SlimPay only in the
TokenId field on the payment method. Zuora automatically populates the value for the
SecondTokenId field according to the value of the Slimpay API
Card-Alias: reference field.
To enable the support for Credit Card Reference Transactions, submit a request at Zuora Global Support.
- EUR (SEPA)
- GBP (Direct Debit UK)
Support for Delayed Capture
The Delayed Capture feature allows you to authorize the availability of funds for a transaction but delay the capture of funds until a later time. Zuora's SlimPay gateway supports Delayed Capture for Credit Card Reference payment methods, which involves the use of the following API operations:
Zuora also supports capturing authorizations that were generated externally to call the Zuora's Create authorization API operation.
Support for Gateway Reconciliation
The SlimPay gateway integration supports the following Gateway Reconciliation event types:
SlimPay supports gateway reconciliation failed payment events, and payment reversals. Gateway Reconciliation job status can be viewed beginning at 02:00 UTC. Any direct debit payment that does not have any direct debit issue associated and has been executed on its execution date, the payment is considered settled. The system will mark these transactions as settled and any rejected payments as rejected and create external refunds for them.
See Gateway Reconciliation and Set up and configure a SlimPay payment gateway instance for more information.
SlimPay gateway integration does not support non-referenced refunds.