PayTo payments

Use PayTo payments in the Pay by Bank App when you want customers to authorise payment directly from their bank account.

PayTo supports three main receive-payment patterns:

Once-off PayTo

A single authorised payment collected directly from the customer’s bank account.

Recurring PayTo

An ongoing payment authority for future recurring collections.

Pay & Subscribe

An upfront payment collected now, with recurring payments authorised for later.

Choose the right PayTo model

Payment model	Best for	What it does
Once-off PayTo	Single authorised payments	Collect one authorised payment from the customer’s bank account
Recurring PayTo	Subscriptions and repeat billing	Establish an ongoing payment authority for future collections
Pay & Subscribe	Upfront payment plus repeat billing	Collect an initial payment and set up an ongoing agreement

How PayTo works

flowchart LR
    A["Customer opens checkoutUrl"] --> B["Selects PayTo"]
    B --> C["Enters PayID or bank details"]
    C --> D["Reviews payment or agreement"]
    D --> E["Authorises in banking app"]
    E --> F["Payment or agreement status updates in checkout"]

Payment patterns

Once-off PayTo

Use Once-off PayTo when you want to collect a single authorised payment from a customer’s bank account.

Best for:

one-time purchases
account settlement
higher-value payments where bank authorisation is preferred

What to expect:

the customer authorises a single payment
the payment is approved through their banking environment
no ongoing payment authority is created

Configure it like this:

create a PayTo payment request for a single payment
do not configure it as a recurring agreement

{
  "amount": 150.00,
  "description": "Order 12345",
  "PaymentAgreementRequest": {
    "clientTransactionId": "your-unique-id",
    "agreementStartDate": "2026-04-13",
    "agreementEndDate": "2026-04-13",
    "agreementFrequency": "ADHOC"
  },
  "successRedirectURL": "https://merchant.example/success",
  "cancelRedirectURL": "https://merchant.example/cancel"
}

Recurring PayTo

Use Recurring PayTo when you want to establish an ongoing payment authority for future collections from the customer’s bank account.

Best for:

subscriptions
memberships
instalment plans
repeat service payments

What to expect:

the customer authorises an ongoing PayTo agreement
future payments can be collected under that agreement
the hosted UX supports repeat payment journeys
where enabled, passkeys can streamline the return payment experience

Configure it like this:

create a PaymentAgreementRequest
set different agreementStartDate and agreementEndDate values
set the recurring agreementFrequency
set agreementMaximumAmount for future recurring collections

{
  "PaymentAgreementRequest": {
    "clientTransactionId": "your-unique-id",
    "agreementStartDate": "2026-04-13",
    "agreementEndDate": "2027-04-13",
    "agreementFrequency": "MONTHLY",
    "agreementMaximumAmount": 50.00
  },
  "successRedirectURL": "https://merchant.example/success",
  "cancelRedirectURL": "https://merchant.example/cancel"
}

Pay & Subscribe

Use Pay & Subscribe when you want to collect an initial payment now and also establish a recurring PayTo agreement for future payments.

Best for:

subscription sign-up flows
memberships with an upfront payment
services that begin immediately and continue on a recurring basis

What to expect:

the customer completes an upfront payment during checkout
the customer also authorises an ongoing PayTo agreement
the flow combines immediate collection with future recurring billing

Configure it like this:

set amount for the payment collected immediately
include a PaymentAgreementRequest for future recurring payments
set the recurring agreementFrequency
set agreementMaximumAmount for future recurring collections

{
  "amount": 20.00,
  "description": "Subscription sign-up",
  "PaymentAgreementRequest": {
    "clientTransactionId": "your-unique-id",
    "agreementStartDate": "2026-04-13",
    "agreementEndDate": "2027-04-13",
    "agreementFrequency": "MONTHLY",
    "agreementMaximumAmount": 50.00
  },
  "successRedirectURL": "https://merchant.example/success",
  "cancelRedirectURL": "https://merchant.example/cancel"
}

Recurring PayTo with passkeys

Recurring PayTo can be enabled for your Pay by Bank App configuration if you want customers to approve an ongoing PayTo agreement and then make future payments with a faster return experience.

Once this configuration is enabled, the PayTo agreement created during checkout is recurring in nature rather than a once-off agreement.

What this means

With recurring PayTo enabled:

the customer completes the initial PayTo agreement setup during checkout
the agreement remains available for future payments
when the customer returns to make a subsequent payment, they do not need to approve the payment again in their banking app
instead, they can use their passkey to complete payment quickly

How passkeys work

Passkeys allow the customer to authenticate using the device and biometric method they already use every day, such as:

Face ID
fingerprint
device PIN
another supported biometric or device credential

This creates a much faster return payment experience.

What the return payment experience looks like

For a returning customer, the journey is simple:

Click to pay
Confirm with their passkey
Pay

In practice, this means the customer can return and complete a subsequent payment using a quick biometric check, rather than being redirected to approve again in their banking app.

sequenceDiagram
    participant C as Customer
    participant PBB as Pay by Bank App
    participant D as Customer Device

    C->>PBB: Return to make another payment
    PBB->>C: Prompt for passkey sign-in
    C->>D: Confirm with Face ID / biometrics
    D-->>PBB: Passkey authenticated
    PBB-->>C: Payment completed

Subscriptions App vs recurring payments in Pay by Bank

Azupay supports recurring PayTo payments in two different ways:

Recurring payments in Pay by Bank
Recurring payments via the Subscriptions App

Both use PayTo, but they are designed for different customer journeys.

Option	Best for	How it works
Recurring payments in Pay by Bank	Merchants who want to collect a payment during checkout and support a faster return payment experience later	The customer starts in the Pay by Bank checkout experience, creates a recurring PayTo agreement, and can return to make future payments
Subscriptions App	Merchants who want to set up an ongoing recurring payment authority first, then initiate collections against that agreement over time	The customer completes a dedicated agreement setup flow, and future payments are initiated against the approved agreement

Use recurring payments in Pay by Bank when

you want recurring capability built into the checkout experience
the customer is already in a pay-now flow and you need to collect payment now
you want to support future return payments with a lower-friction experience
you may want to support passkeys for subsequent payments

Use the Subscriptions App when

your primary goal is to set up a recurring PayTo agreement
you want a dedicated agreement setup journey
you plan to initiate recurring payments against that agreement over time
the agreement itself is the main product flow, rather than a checkout payment

The key difference

The main difference is the starting point:

Pay by Bank recurring payments start from a checkout and payment experience
Subscriptions App starts from an agreement setup experiencer

If you want to collect an upfront payment and also establish a recurring agreement in the same journey, use the Pay by Bank App rather than the Subscriptions App.

What the customer sees

The hosted Pay by Bank App guides the customer through the full PayTo journey, including:

entering their payment details
reviewing the payment or agreement
authorising in their banking app
seeing payment or agreement status updates in checkout

Use the checkoutUrl

Once your Payment Request has been created, use the returned checkoutUrl to direct the payer into the hosted Pay by Bank App experience.

The checkout experience will:

present the payment or agreement details to the payer
guide them through the PayTo authorisation flow
support once-off or recurring payment journeys depending on configuration
reflect the payment or agreement status through the hosted UX