- Getting Started
- Standalone 3D Secure
- Mobile SDK
- First Integration
- Set Up Your Server
- Ready-to-Use UI
- SDK & Your Own UI
- 3D Secure 2.x
- Apple Pay
- Google Pay
- Klarna Payments
- Manage Payments
- ReD Shield
- API Reference
- Result Codes
- Brands Reference
With Scheduling API, you can schedule DB, PA or CD transaction in the future.
NOTE: You should be fully PCI compliant if you wish to perform tokenization requests server-to-server (as it requires that you collect the card data).
How it works
1. Store the payment data
Following is an example of stand alone registration.
2. Schedule a payment
Send a request to /schedules end point with the registrationId, payment type and the job schedule which describes when and how often the transaction should be committed.
For complete reference of job parameters, check API Parameters Reference:
3. We execute the transaction for you
As the scheduled transaction triggers, the system commits the payment transaction on time using the stored payment information and payment type specified.
The system will commit a payment transaction with the paymentType, amount and currency specified, and will use the payment information registered on the first step.
4. Cancel the schedule
As the case of canceling the scheduled transaction, merchant sends a deschedule request to cancel future transactions.
Send a request to the de-scheduling specifying the referenceId of the scheduled transaction as following: