PayTo

PayTo is a real-time, account-to-account payment method built on Australia's New Payments Platform (NPP). It enables merchants to accept both one-off and recurring payments directly from shoppers' bank accounts with real-time authorization through banking apps, lower processing costs, and flexible mandate management.

Payment type	Payment flow	Countries	Currencies	Recurring	Refunds	Partial refunds	Multiple partial refunds	Separate captures	Partial captures	Multiple partial captures	Chargebacks
Real-time payments	Direct	AU	AUD

Add PayTo as a payment method

Enable PayTo for your merchant account using the Management API.

Management API

Make a POST /paymentMethodSettings request and include:

Parameter	Required	Description	Example
type		Must be payto.	payto
payto.merchantName		Business name displayed in shopper's banking app.	ACME Subscriptions Pty Ltd
payto.payToPurpose		Default purpose code (see valid values below).	retail
businessLineId		Conditional: Your business line identifier. Optional, unless you are using the platform model.	SE12345678912345ABCDEFG
storeIds		Conditional: Only required when configuring the payment method for a specific store.	["ST123..."]

PayTo setup is asynchronous. To confirm PayTo was added:

1. Configure a payment method webhook via Customer Area or Management API.
2. Listen for the paymentMethod.created event.

Example webhook confirmation:

If the status is success, PayTo is ready for use.

For webhook configuration, see Configure and manage webhooks.

Payments flow

A typical payment flow includes:

First payment

1. Call /paymentMethods to confirm which payment methods are available for the payment, showing PayTo if included in the response.
2. Collect customer details and submit a /payments request with the appropriate details. Adyen creates an agreement with the customer's bank.

3. The customer will be shown a pending screen while they confirm the payment in their banking app. Successful payment is confirmed via webhook notification from Adyen.

   First payment and mandate creation

   CnNlcXVlbmNlRGlhZ3JhbQphdXRvbnVtYmVyCnBhcnRpY2lwYW50IFNob3BwZXIKcGFydGljaXBhbnQgTWVyY2hhbnQKcGFydGljaXBhbnQgQWR5ZW4KcGFydGljaXBhbnQgTlBQCnBhcnRpY2lwYW50IEJhbmsKCiAgICAlJSBTdGVwIDE6IENoZWNrIFBheW1lbnQgTWV0aG9kcwogICAgTWVyY2hhbnQtPj5BZHllbjogUE9TVCAvcGF5bWVudE1ldGhvZHMgKGNvdW50cnlDb2RlOiBBVSwgc2hvcHBlclJlZmVyZW5jZSkKICAgIEFkeWVuLS0+Pk1lcmNoYW50OiBQYXlUbyBpbmNsdWRlZCBpbiByZXNwb25zZQogICAgTWVyY2hhbnQtPj5TaG9wcGVyOiBEaXNwbGF5IFBheVRvIG9wdGlvbgoKICAgICUlIFN0ZXAgMjogSW5pdGlhdGUgUGF5bWVudCAmIE1hbmRhdGUKICAgIFNob3BwZXItPj5NZXJjaGFudDogUHJvdmlkZXMgUGF5SUQgb3IgQlNCLCBpbml0aWF0ZXMgcGF5bWVudAogICAgTWVyY2hhbnQtPj5BZHllbjogUE9TVCAvcGF5bWVudHMgKHNob3BwZXJBY2NvdW50SWRlbnRpZmllciwgbWFuZGF0ZSwgc3RvcmVQYXltZW50TWV0aG9kOiB0cnVlKQogICAgQWR5ZW4tLT4+TWVyY2hhbnQ6IHJlc3VsdENvZGU6IFBlbmRpbmcgKyBhY3Rpb24gKGF3YWl0KQogICAgTWVyY2hhbnQtPj5TaG9wcGVyOiBTaG93IHBlbmRpbmcgc2NyZWVuCgogICAgJSUgU3RlcCAzOiBNYW5kYXRlIEFwcHJvdmFsIHZpYSBOUFAgJiBCYW5rCiAgICBBZHllbi0+Pk5QUDogQ3JlYXRlIG1hbmRhdGUgcmVxdWVzdAogICAgTlBQLT4+QmFuazogUHVzaCBub3RpZmljYXRpb24KICAgIEJhbmstPj5TaG9wcGVyOiBNYW5kYXRlIGFwcHJvdmFsIHJlcXVlc3QgKGJhbmtpbmcgYXBwKQogICAgU2hvcHBlci0+PkJhbms6IENvbmZpcm1zIG1hbmRhdGUKICAgIEJhbmstPj5OUFA6IE1hbmRhdGUgY29uZmlybWVkCiAgICBOUFAtLT4+QWR5ZW46IENvbmZpcm1hdGlvbgoKICAgICUlIFN0ZXAgNDogRmlyc3QgUGF5bWVudCBFeGVjdXRpb24gJiBXZWJob29rcwogICAgQWR5ZW4tPj5OUFA6IEV4ZWN1dGUgZmlyc3QgcGF5bWVudAogICAgTlBQLT4+QmFuazogRGViaXQgYWNjb3VudAogICAgQmFuay0tPj5OUFA6IFN1Y2Nlc3MKICAgIE5QUC0tPj5BZHllbjogUGF5bWVudCBzdWNjZXNzZnVsCiAgICBBZHllbi0tPj5NZXJjaGFudDogQVVUSE9SSVNBVElPTiB3ZWJob29rIChwYXltZW50IG91dGNvbWUgKyByZWN1cnJpbmdEZXRhaWxSZWZlcmVuY2UpCiAgICBBZHllbi0tPj5NZXJjaGFudDogUkVDVVJSSU5HX0NPTlRSQUNUIHdlYmhvb2sgKHRva2VuIC8gcHNwUmVmZXJlbmNlIGZvciBmdXR1cmUgcGF5bWVudHMpCiA=

   One-time payment

   CnNlcXVlbmNlRGlhZ3JhbQphdXRvbnVtYmVyCnBhcnRpY2lwYW50IFNob3BwZXIKcGFydGljaXBhbnQgTWVyY2hhbnQKcGFydGljaXBhbnQgQWR5ZW4KcGFydGljaXBhbnQgTlBQCnBhcnRpY2lwYW50IEJhbmsKCiAgICAlJSBTdGVwIDE6IEluaXRpYWwgQ2hlY2sKICAgIE1lcmNoYW50LT4+QWR5ZW46IFBPU1QgL3BheW1lbnRNZXRob2RzIChjb3VudHJ5Q29kZTogQVUpCiAgICBBZHllbi0tPj5NZXJjaGFudDogUGF5VG8gaW5jbHVkZWQgaW4gcmVzcG9uc2UKICAgIE1lcmNoYW50LT4+U2hvcHBlcjogRGlzcGxheSBQYXlUbyBvcHRpb24KCiAgICAlJSBTdGVwIDI6IFBheW1lbnQgSW5pdGlhdGlvbiAmIE5vdGUKICAgIFNob3BwZXItPj5NZXJjaGFudDogUHJvdmlkZXMgUGF5SUQgb3IgQlNCCiAgICBNZXJjaGFudC0+PkFkeWVuOiBQT1NUIC9wYXltZW50cyAoc2hvcHBlckFjY291bnRJZGVudGlmaWVyLCBzaG9wcGVyU3RhdGVtZW50LCBubyBtYW5kYXRlKQogICAgTm90ZSBvdmVyIEFkeWVuOiBBdXRvLWdlbmVyYXRlcyBtYW5kYXRlIChhZGhvYywgZW5kRGF0ZTogRGF5KzEsIGFtb3VudFJ1bGU6IGV4YWN0LCBjb3VudDogMSkKICAgIEFkeWVuLS0+Pk1lcmNoYW50OiByZXN1bHRDb2RlOiBQZW5kaW5nICsgYWN0aW9uIHdpdGggYXV0by1nZW5lcmF0ZWQgbWFuZGF0ZQogICAgTWVyY2hhbnQtPj5TaG9wcGVyOiBTaG93IHBlbmRpbmcgc2NyZWVuCgogICAgJSUgU3RlcCAzOiBBdXRob3JpemF0aW9uICYgU2luZ2xlLVVzZSBNYW5kYXRlIENyZWF0aW9uCiAgICBBZHllbi0+Pk5QUDogQ3JlYXRlIHNpbmdsZS11c2UgbWFuZGF0ZQogICAgTlBQLT4+QmFuazogUHVzaCBub3RpZmljYXRpb24KICAgIEJhbmstPj5TaG9wcGVyOiBBcHByb3ZhbCByZXF1ZXN0IChiYW5raW5nIGFwcCkKICAgIFNob3BwZXItPj5CYW5rOiBDb25maXJtcwogICAgQmFuay0+Pk5QUDogQ29uZmlybWVkCiAgICBOUFAtLT4+QWR5ZW46IENvbmZpcm1hdGlvbgoKICAgICUlIFN0ZXAgNDogRXhlY3V0aW9uICYgRmluYWwgV2ViaG9vawogICAgQWR5ZW4tPj5OUFA6IEV4ZWN1dGUgcGF5bWVudAogICAgTlBQLT4+QmFuazogRGViaXQgYWNjb3VudAogICAgQmFuay0tPj5OUFA6IFN1Y2Nlc3MKICAgIE5QUC0tPj5BZHllbjogUGF5bWVudCBzdWNjZXNzZnVsCiAgICBBZHllbi0tPj5NZXJjaGFudDogQVVUSE9SSVNBVElPTiB3ZWJob29rCiA=

Subsequent payments

1. Call /paymentMethods providing the shopperReference to retrieve your customer's stored payment methods.
2. Present the payment methods for which the available supportedRecurringProcessingModels contains CardOnFile to your customer.
3. Submit a /payments request with the appropriate details including the stored payment token. Adyen will automatically process the payment.
4. The customer will be able to see the transaction in real-time in their banking app. Successful payment is confirmed via webhook notification from Adyen.

When retrieving payment methods with a shopperReference, filter which PayTo tokens to show:

• Show at checkout (customer-initiated): Tokens with supportedRecurringProcessingModels containing CardOnFile

• Do not show at checkout (merchant-initiated): Tokens with only Subscription or UnscheduledCardOnFile

  Subsequent recurring payment (CardOnFile)

  CnNlcXVlbmNlRGlhZ3JhbQphdXRvbnVtYmVyCnBhcnRpY2lwYW50IFNob3BwZXIKcGFydGljaXBhbnQgTWVyY2hhbnQKcGFydGljaXBhbnQgQWR5ZW4KcGFydGljaXBhbnQgTlBQCnBhcnRpY2lwYW50IEJhbmsKCiAgICAlJSBTdGVwIDE6IEZldGNoIFNhdmVkIFBheW1lbnQgTWV0aG9kcwogICAgTWVyY2hhbnQtPj5BZHllbjogUE9TVCAvcGF5bWVudE1ldGhvZHMgKHNob3BwZXJSZWZlcmVuY2UpCiAgICBBZHllbi0tPj5NZXJjaGFudDogc3RvcmVkUGF5bWVudE1ldGhvZHMgd2l0aCBzdXBwb3J0ZWRSZWN1cnJpbmdQcm9jZXNzaW5nTW9kZWxzCiAgICBNZXJjaGFudC0+PlNob3BwZXI6IERpc3BsYXkgQ2FyZE9uRmlsZSB0b2tlbnMgb25seQoKICAgICUlIFN0ZXAgMjogUGF5bWVudCBJbml0aWF0aW9uCiAgICBTaG9wcGVyLT4+TWVyY2hhbnQ6IFNlbGVjdHMgc2F2ZWQgUGF5VG8sIGNsaWNrcyBQYXkKICAgIE1lcmNoYW50LT4+QWR5ZW46IFBPU1QgL3BheW1lbnRzIChyZWN1cnJpbmdEZXRhaWxSZWZlcmVuY2UsIHNob3BwZXJJbnRlcmFjdGlvbjogQ29udEF1dGgpCiAgICBBZHllbi0tPj5NZXJjaGFudDogcmVzdWx0Q29kZTogUGVuZGluZyArIGFjdGlvbiAoYXdhaXQpCgogICAgJSUgU3RlcCAzOiBQYXltZW50IEV4ZWN1dGlvbgogICAgQWR5ZW4tPj5OUFA6IEV4ZWN1dGUgcGF5bWVudCB1c2luZyBleGlzdGluZyBtYW5kYXRlCiAgICBOUFAtPj5CYW5rOiBEZWJpdCBhY2NvdW50CiAgICBCYW5rLT4+U2hvcHBlcjogUGF5bWVudCBub3RpZmljYXRpb24gKHJlYWwtdGltZSkKICAgIEJhbmstLT4+TlBQOiBTdWNjZXNzCiAgICBOUFAtLT4+QWR5ZW46IFBheW1lbnQgc3VjY2Vzc2Z1bAogICAgQWR5ZW4tLT4+TWVyY2hhbnQ6IEFVVEhPUklTQVRJT04gd2ViaG9vawog

Recurring processing models

PayTo supports three recurring processing models. Select a model based on your payment frequency:

Important:

• Subscription mandates require a count parameter (payments per frequency period)
• Adhoc mandates can omit count for unlimited payments
• The recurringProcessingModel must match your mandate.frequency:
  • Scheduled frequency: use Subscription
  • Adhoc frequency: use CardOnFile or UnscheduledCardOnFile

For detailed guidance, see How to choose recurring processing model.

Transaction limits

PayTo payments in Australia are subject to varying transaction limits that differ among banks and depend on the payment type:

• Subscription (Recurring) Payments: Many banks set a limit of $1,000 per transaction for recurring PayTo payments. However, some banks allow higher limits, up to $25,000 for recurring transactions.
• One-Off (Ad hoc) Payments: One-off payments typically have higher limits. Many banks allow one-off PayTo payments of up to $25,000. However, some banks may set lower limits for one-off payments, with daily limits as low as $5,000.
• Card On File (Ad hoc) Payments: Often have higher limits where many banks allow ad hoc PayTo payments of up to $25,000. However, some banks may set lower limits for ad hoc payments, with daily limits up to $1,000.

It is important to note that these limits can vary based on factors such as account type, customer verification status, and individual bank policies. Additionally, some banks may allow customers to request higher limits upon verification.

Post-transaction management

Mandate management

Cancellations: Customers can cancel mandates anytime through their banking app. You'll receive a DISABLE_RECURRING webhook and future payments will fail. You cannot prevent customer-initiated cancellations.

Mandate Cancellation

Modifications: Mandates cannot be modified after creation. To change terms (amount, frequency, end date), cancel the existing mandate and create a new one with customer authorization.

Refunds

Both full and partial refunds are supported. Refunds cannot be reversed once processed. Verify amounts and recipient details before initiating.

Disputes

Unlike card payments, no chargeback process exists to clawback PayTo payments. If your customers wish to challenge the withdrawal of funds from their bank account, they do so via a manual mandate claim process with their bank. Note that mandate claims are largely limited to the exceptional scenarios:

1. Where there is no record of the customer’s mandate authorization
2. If the relevant mandate is suspended or canceled at the time of payment

Best practice: Resolve claims directly with your customer and offer refunds where appropriate.

Bank notifications

The shopper can expect to receive in-app and/or email notifications from their bank for both one-off and recurring payments that are made with PayTo. These notifications could be for the creation or cancellation of mandates and agreements.

For One-Off (Ad hoc) Payments, a shopper might receive a notification for agreement creation, and then another notification for the cancellation of the agreement. This happens because cancellation will automatically occur once the agreement has elapsed, which happens immediately for one-time payments.
How this is communicated to the shopper depends on the financial institution they’re with.

Common errors and refusals

PayTo provides detailed raw responses that can be used as feedback to optimize your shopper checkout experience.
Best practice: Enable raw acquirer response and see PayTo raw responses for error and refusal handling.

How do you want to integrate?