Documentation
Request a demo

Card method

Choose the right card payment flow to balance customer experience.

Card Payments

Card payments are one of the most widely used Payment methods and can be integrated into the Checkout, Host to Host payments and Hosted fields in different ways depending on your business needs. Our platform supports two main card payment flows:

  • Native flow (Direct): collect card details directly on the platform.
  • Redirect flow: redirect customers to another Checkout.

Each flow offers a different balance of control, implementation effort, and customer experience.

Card Native flow

Card Native flow allows your Customers to directly use your Checkout, without being redirected.

The flow is designed for Merchants who want more control over the payment experience and a more seamless Customer journey. It allows Customers to enter their card details directly at Checkout while keeping the payment process integrated into your branded interface.

When to use? How to use? Customer experience
Use the Card Native flow if you want to:
  • Keep Customers on your Checkout during payment
  • Create a more seamless and branded payment experience
  • Reduce friction before Authentication
  • Build a more customisable Checkout experience
 With Card Native flow, the payment journey happens directly within Checkout.

Payment flow overview:
  1. The Customer opens the Checkout page.
  2. The card payment form is displayed directly within the Checkout.
  3. The Customer enters their card details.
  4. The payment is submitted for processing.
  5. If required, the Customer completes additional authentication, such as 3D Secure.
  6. The final payment result is returned to your Checkout.
 Card Native flow is designed to provide a more integrated Checkout experience.

With this payment flow:
  • The Customer remains on your Checkout during card entry.
  • Payment details are entered directly within the Checkout form.
  • The payment step feels more native to your website or application.
  • Authentication is triggered only when required.
The flow is best suited for Merchants who want greater control over how card payments are presented and processed within the Checkout. This allows the Customer to stay within your Checkout throughout the payment process, except where additional issuer-side authentication is required. This can help reduce disruption in the Checkout journey and create a more consistent payment experience.

Card Redirect flow

Card Redirect flow allows you to process card payments using another Checkout. This approach simplifies integration and reduces the need to handle payment form logic directly within your application.

It is designed for Merchants who want a faster setup with minimal frontend implementation while ensuring a secure and compliant payment experience.

When to use? How to use? Customer experience
Use Card Redirect flow if you want to:
  • Launch quickly with minimal development effort
  • Avoid maintaining the payment form
  • Reduce frontend complexity
  • Rely on a hosted and managed payment page
  • Simplify security and compliance responsibilities
 With Card Redirect flow, the payment journey happens with redirection to a different HPP.

Payment flow overview:
  1. The Customer initiates a payment on your website or app.
  2. The Customer is redirected to another Checkout.
  3. The Customer enters their card details.
  4. The payment is processed.
  5. If required, the Customer completes 3D Secure authentication.
  6. The Customer is redirected back to your website.
  7. The payment result is returned via redirect and/or Webhook.
 With this payment flow:
  1. Customer is redirected to another Checkout.
  2. Payment form is handled outside the Checkout.
  3. Customer returns to your website after payment completion.
Redirect flow is for Merchants who prioritise speed of integration and operational simplicity. This flow removes the need to handle card input directly in your checkout. This flow adds an extra step in the journey, but it simplifies the overall implementation.

Compare Card Native VS Card Redirect

The primary choice between the Card method flow largely depends on your business needs. Thus, take a look at the table below to grasp the main differences and align them with your priorities.

Feature Card Native flow Card Redirect flow
Customer experience Customer stays on your site Customer gets redirected
UI control Full control Limited control
Card data handling Within our system Handled by hosted page & Provider

Updated about 1 hour ago