- Get Started
- Guides
- Integrations
- References
- API Reference
- Basic Payment
- Forex
- Authentication
- Card Account
- Apple Pay
- Virtual Account
- Bank Account
- Token Account
- Customer
- Billing Address
- Merchant Billing Address
- Shipping Address
- Merchant Shipping Address
- Merchant
- Corporate
- Recipient
- Marketplace & Cart
- Airline
- Lodging
- Passenger
- Tokenization
- Recurring Migration
- 3D Secure
- Custom Parameters
- Async Payments
- Job
- Risk
- Point of Sale
- Response Parameters
- Card On File
- Chargeback
- Result Codes
- Payment Methods
- Transaction Flows
- Regression Testing
- Data Retention Policy
- API Reference
- Support
Features FAQ
What is meant by transparent clearing?
The Open Payment Platform simplifies capturing and clearing by providing a unified integration, which hides potential complications of different methods of clearing for different upstream connectors (e.g. batch files or different formats).
Where can I find more information on 3D secure?
We have a 3D secure guide, here.
Can I use my own 3D Secure MPI?
Yes. When submitting requests server-to-server, you can send the 3D secure authentication data in the threeDSecure object (example below). When using COPYandPAY you can choose to enable our MPI built into the payment form.
threeDSecure.eci //ECI Indicator threeDSecure.verificationId //CAVV or AAV threeDSecure.xid //3D Secure Transaction ID
What methods of payment are supported?
We support the following methods of payment:
Brand | Async / sync workflow |
---|