Skip to main content
The Payment Sessions API is a unified solution for payment collection across one-time payments and recurring payments.

Use Cases

See how Payment Sessions map to common business scenarios.

Lifecycle

Understand the states a payment session moves through from creation to completion.

Webhooks

React to session events in real time.

​
Key Features

  • Flexible Payment Flows: Handle one-time payments, first-time setup payments for subscriptions, and repeat payments with minimal effort.
  • Seamless Recurring Payments: Use saved payment methods for a series of transactions initiated and completed without customer interaction.

​
Benefits

  • Simplicity: Manage various payment scenarios with a single API.
  • Customizability: Tailor the payment experience to fit your brand.
  • Scalability: Support a variety of payment methods and grow your business globally.

​
How It Works

1

Create a Payment Session

Start by creating a payment session with all necessary details like amount, currency, and payment type.
2

Redirect if Required

For payments where the customer is present, redirect them to the checkout page provided in the session_url to complete the payment. For recurring payments where the customer is not present, use the customer’s saved payment method to process the payment without any customer interaction.
3

Track Payment Status

Monitor the status of your payments in real time using webhooks or API calls.

​
Session Types

The API supports three distinct session types to handle both customer-present and customer-not-present payments:
  • one_time: A one-time payment where the customer is present and completes payment in real time. Optionally saves the payment method for future customer-present use.
  • first_in_series: The first payment in a series, where the customer is present and authorises their payment method for future merchant-initiated payments. This authorisation is called a mandate, and is typically used to set up recurring payments such as subscriptions or instalment plans.
  • next_in_series: A subsequent payment in a series, where the customer is not present. Fully programmatic, no customer interaction required.
A mandate is an authorisation that allows a merchant to initiate future payments when the customer is not present in the flow.
The following table summarises the differences:
one_timefirst_in_seriesnext_in_series
Primary PurposeOne-time payment by the customer.First payment to set up future automatic payments.Next payment in a series.
Customer InteractionRequired (customer is present).Required (customer is present).Not required (customer is absent).
Saving Payment MethodOptional (for customer present use).Mandatory (for customer absent use).Not applicable (uses saved method).
Payment FlowCustomer completes via Checkout page.Customer completes via Checkout page.Payment processed programmatically.
ExamplesOne-off purchase with the option to save for future purchases.Subscription setup or instalment plan.Monthly subscription payment or utility bill.