- 20 Feb 2025
- 2 Minutes to read
- Print
- DarkLight
Payment Solution Comparison
- Updated on 20 Feb 2025
- 2 Minutes to read
- Print
- DarkLight
Integration Types
Use this page to compare the features of our integration solutions:
- Hosted Payment Page
- Payment Operations API ( requires `'SAQ D PCI certification' when processing card payments with raw card data)
- Payment Links
Payment Flow
Hosted Payment Page and Payment Links are comprehensive, end-to-end solutions that manage card tokenization, processing of Alternative Payment Methods, payment requests, and authentication seamlessly.
The Payments Operations API requires a higher level of technical integration effort, including the implementation and management of 3D Secure authentication.
Integrated payment methods
- Our Hosted Payment Page and Payments Links accept cards payments (Visa & Mastercard) along with a full list of Alternative Payment Methods.
- Our Payments API supports the payment types detailed in the table below:
Payment Flow | Supported Methods |
---|---|
Deposit | Card Transactions |
Withdrawal | Card Transactions Alternative Payment Methods |
Payment form configuration
Our hosted payment page presents customers with a payment form that offers diverse configuration and customisation options. Upon completing the payment, both the hosted payment page and payment links will redirect customers to a designated URL.
PCI DSS certification level
To process payments using the full card details via the Payments API, you must have 'SAQ D PCI Compliance'
.
If you do not have the necessary PCI DSS certification, you must use our hosted payment page or Payment Links to collect raw card data.
Solution Comparison Table
The table below outlines the available payment processing options for each product, along with the corresponding technical effort required and PCI responsibilities.
Integration Method | Payment Processing | Support Transaction Types | Technical Effort Needed | Card Data Collection | PCI Responsibilities |
---|---|---|---|---|---|
Hosted Payment Page | Card Payments, APMs | Auth , Purc | Minimal effort needed for integration. The hosted page will handle the end-to-end flow of the transaction including the 3D-Secure authentication where applicable. Capt , Refund , OrginalCredit and Voids must be processed via the Payments API as no customer input is required. | We handle the card data. The customer enters the card details directly on our page | As we host the webpage, the responsibility for PCI Compliance falls on us. |
Payment Operations API | Card Payments | Auth , Capt* , Purc , Refund* , OrginalCredit* , void* | High effort for integration including the handling of 3DS authentication. | The merchant will collect the card information. | Submit a detailed SAQ-D form and potentially even require full PCI DSS certification. |
Payment Links currently being implemented* | Card Payments, APMs | Auth , Purc | No effort. Generate payment links via our merchant portal. This can then be shared with the customer. It is also possible to create payment links using our APIs. | We handle the card data. The customer will enter the card details directly on our hosted page. | As we host the webpage, the responsibility for PCI Compliance falls on us. |
These transaction types typically do not require PCI compliance, provided that the card details were initially captured on the hosted payment page during authorisation or purchase.
You can find the API details here.