Overview of SlimPay payment gateway integration
Supported features
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 |
| Supported payment operations | Validate Payment Method, Payment, Void Payment, Referenced refund |
| Support 3D Secure 2.0 | No |
| Support Delayed Capture | Yes |
| Support Gateway Options fields | No |
| SlimPay payment gateways endpoint used for Zuora gateway integration service |
|
| Support Batch Gateway Reconciliation | Yes |
| SlimPay production endpoint used for Gateway Reconciliation service | slimprod.slimpay.net:6321 |
| Support Payment Method Updater | No |
Supported payment methods
The SlimPay payment gateway integration supports SEPA payment methods. For more information about setting up payment methods in Zuora, see Define and set up payment methods.
When creating a payment method, it is recommended to associate the payment method with an account. For payment methods created through API operations, specify the accountKey field. For payment methods created through hosted payment method pages, specify the field_accountId client parameter in the request. If the account number is not specified, the subscriber.reference field in the request to SlimPay will be set to accountHolderLastName+accountHolderFirstName+randomId. If the account number is specified, the subscriber.reference field will be set to the account number in Zuora.
Support for mandate creation
Zuora supports mandate creation for SEPA payment methods. Zuora will generate and pass the mandate to the gateway.
Supported currencies
- 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. For how to use the Delayed Capture feature, see Payment Authorization in Zuora API Reference.
Support for Batch Gateway Reconciliation
The SlimPay gateway integration supports the following Gateway Reconciliation event types:
- Settlement
- Rejection
A direct debit payment is considered settled if it has no associated direct debit issues and was executed on its execution date. A rejected payment is marked as rejected, and external refunds are created.
SlimPay uploads the reconciliation file daily at 05:00 AM UTC and Zuora schedules the Gateway Reconciliation job at 05:30 AM UTC to fetch the file. Zuora reconciles transactions at 22:30 PST daily.
Zuora incorporates a retry mechanism to fetch the Gateway Reconciliation file from the gateway server. If the file is not available on the gateway server at the time of the fetch, the "Source Not Present" message is displayed. This message indicates that the file has not yet been uploaded to the gateway server and is an expected behavior to handle cases where gateways upload files at varying times. Once the file is available on the gateway server, Zuora fetches and processes it. Note that processing the file may take time, so "Source Not Present" may still appear in Zuora temporarily, even if the file is already available on the gateway server.
If the Batch Gateway Reconciliation feature was enabled on your gateway instance before the 2024.Q4.0.3 release, complete the following steps to ensure the updated daily job schedule introduced in this release takes effect. Otherwise, the "Source Not Present" error occurs, and you will need to work with SlimPay to manually upload the reconciliation file.
- Navigate to the gateway instance configuration page.
- Turn off the Enable Reconciliation setting and save the change.
- Turn on the Enable Reconciliation setting again and save the change.
See Gateway Reconciliation and Set up and configure a SlimPay payment gateway instance for more information.
Limitation
SlimPay gateway integration does not support non-referenced refunds.