Skip to main content

Flow Overview

Learn about how payment flows work in Odus and the different participants involved in the process. Your application needs to be ready to handle these flows to ensure a smooth payment experience for your customers.

There are two main payment flows that must be integrated into your application: the Basic Flow and the Redirect Flow.

Both flows involve multiple participants:

  1. Customer: The end user making the payment.
  2. Merchant Frontend: The merchant's web application where the customer initiates the payment.
  3. Odus Checkout SDK: The SDK that handles secure payment processing.
  4. Merchant Backend: The merchant's server that communicates with the Odus API.
  5. Odus API: The backend service that processes payments and interacts with the Payment Service Providers (PSPs).
  6. Payment Service Provider (PSP): The third-party service that processes the payment on behalf of the merchant.

Basic Flow​

This flow covers card payments without 3DS authentication. It includes the following steps:

Redirect Flow​

Redirect flow is used for payments that require the customer to be redirected to a third-party page, such as for 3DS authentication or PayPal payments.

warning

Unlike the basic payment flow, the Checkout SDK won't handle the payment result for redirect flows. The customer is redirected to the merchant's return URL, and the merchant backend must verify the final payment status by calling the Odus API. The SDK will not emit onPaymentSucceeded or onPaymentFailed events in this case.

You can read more about it in the Redirect Flow Guide.

3DS Authentication Flow​

This flow covers card payments that require 3DS authentication, which involves redirecting the customer to a secure page for authentication provided by the Payment Service Provider (PSP). The flow includes the following steps:

PayPal Flow​