Card ECOM

Card ECOM is a merchant's decision to take a specific type of payment card, like a credit or debit card, from a customer. Choose an integration option below to get started — from Payment Page Redirect to Server-to-Server, Checkout Page, and Pay by Link.

Networks	Features	Integrations	payment_type
Visa, Mastercard	Payment Authorize Capture Refund Partial refund Reverse Register Recurring	Server-to-Server Checkout Page Pay by Link Payment Page Redirect	cardecom

Payment workflow

The following diagrams explain the Card ECOM payment workflows for Payment Page Redirect and Server-to-Server.

Payment Page Redirect

Card ECOM — Payment Page Redirect

Scroll horizontally if the diagram is wider than your screen.

1. 1
   Payer (Cardholder)→Merchant

   1. Initiates transaction

2. 2
   Merchant→OneAPI

   2. Create payment request (Payment API)

3. 3
   OneAPI→Merchant

   3. Response with client_action: redirect (payment page URL)

4. 4
   Merchant→Payer (Cardholder)

   4. Redirect to Hosted Payment Page

5. 5
   Payer (Cardholder)→OneAPI

   5. Enters card & cardholder data

6. i
   OneAPI

   3DS is not mandatory in all jurisdictions — steps 6–9 apply only when 3DS is required; a frictionless authentication skips the challenge

7. 6
   OneAPI→Card Issuer

   6. 3DS authentication request

8. 7
   Card Issuer→Payer (Cardholder)

   7. 3DS challenge (redirect)

9. 8
   Payer (Cardholder)→Card Issuer

   8. Confirms 3DS challenge

10. 9
    Card Issuer→OneAPI

    9. 3DS authentication result

11. 10
    OneAPI→OneAPI

    10. Processes payment

12. 11
    OneAPI→Payer (Cardholder)

    11. Redirect to success_url or error_url

13. i
    OneAPI

    Payment processing occurs asynchronously

14. 12
    OneAPI→Merchant

    12. Postback notification (payment status update)

15. 13
    Merchant→Merchant

    13. Update order status in system

Server-to-Server

Card ECOM — Server-to-Server (own MPI)

Scroll horizontally if the diagram is wider than your screen.

1. 1
   Payer (Cardholder)→Merchant

   1. Initiates transaction

2. 2
   Merchant→OneAPI

   2. Create payment request with card data (Payment API)

3. 3
   OneAPI→OneAPI

   3. Processes payment using merchant's 3DS data

4. 4
   OneAPI→Merchant

   4. Payment result (status: completed)

5. i
   OneAPI

   A postback is still sent for the final status

6. 5
   OneAPI→Merchant

   5. Postback notification (payment status update)

7. 6
   Merchant→Merchant

   6. Update order status in system

Card ECOM — Server-to-Server (gateway 3DS)

Scroll horizontally if the diagram is wider than your screen.

1. 1
   Payer (Cardholder)→Merchant

   1. Initiates transaction

2. 2
   Merchant→OneAPI

   2. Create payment request with card data (Payment API)

3. 3
   OneAPI→Merchant

   3. Response (status: pending, client_action: postForm)

4. 4
   Merchant→Payer (Cardholder)

   4. Redirect to 3DS authentication page (postForm)

5. 5
   Payer (Cardholder)→Card Issuer

   5. Completes 3DS challenge

6. 6
   Card Issuer→OneAPI

   6. 3DS authentication result

7. 7
   OneAPI→OneAPI

   7. Processes payment

8. 8
   OneAPI→Payer (Cardholder)

   8. Redirect to success_url or error_url

9. i
   OneAPI

   Payment processing occurs asynchronously

10. 9
    OneAPI→Merchant

    9. Postback notification (payment status update)

11. 10
    Merchant→Merchant

    10. Update order status in system

Integration options

Choose how you want to accept Card ECOM:

Payment Page Redirect

Create a payment via the Payment API and redirect the customer to the hosted payment page. Card data stays on our PCI DSS compliant page.

Start integrating

Server-to-Server

Send cardholder data directly to OneAPI via the Payment API. Requires PCI DSS compliance on your side.

Start integrating

Checkout Page

Create a checkout session and redirect customers to the hosted checkout. Card ECOM is available among the configured payment methods.

Start integrating

Pay by Link

Share a Pay by Link with your customer. When enabled on the channel, they can pay with Card ECOM on the checkout.

Start integrating