Establish the deposit intent clearly where the customer starts a top-up, before any payment method is chosen.

Show Pay by Bank as a payment method that sets the expectation of paying from the bank. Use the name Pay by Bank in the selector, never Instant Bank Transfer, Bank Transfer or another name (Payment method name).

Default to Pay by Bank with SIP when no account is on file. The customer is trying to complete a task, not to configure long-term permissions.

If an account is saved, default to One Tap deposits. Always allow changing the payment method, but do not ask every time.

Confirm success first. Only then suggest saving the account as an optimisation for next time.

If your business logic and app support auto top-ups, only use AoF. Always notify customers when a payment will be taken, and once it is confirmed. Let customers stop auto top-ups, and provide a reversal mechanism where applicable.

Offer saving an account as a way to make future deposits easier. Always allow skipping.

Use AoF as the primary option. This context signals future intent.

When a card or another bank is already set up, position saving the bank account as an upgrade. Never migrate automatically.

Customers who paid with the legacy bank-payment journey must set up again: it is a new journey, not a rename. Keep Pay by Bank as the label in the payment method selector, with the old name as temporary supporting text only for customers who saw it (Transitioning from “Instant Bank Transfer”).

Make setting up again the primary action, and do not treat these customers as first-time users.

A one-time payment needs priming the first time. Customers still need to understand what happens next before they leave the app. Set three expectations:

1. They will be redirected to their banking app or website.
2. The approval applies only to this amount.
3. They will come back to the app once the payment is completed or cancelled.

Wording, from Mandatory inclusions:

Explain the benefit (One Tap next time), that saving is optional, and that the connection can be removed anytime. Keep limits out of this explanation; if limits apply, show them separately (DEP-PRI-03).

Wording, from One Tap and returning payments:

Where saved-account limits apply, tell the customer before consent, so a limit never surprises them at payment. Keep it separate from the explanation of saving (DEP-PRI-02).

Anchor the value to the next deposit. When the customer returns from the bank, make sure they understand the outcome of the payment before suggesting they save the account. If you can, tailor the message to the bank they just paid with.

Wording, from the save-an-account scenario:

Primary action: Save my account for One Tap.

When a card expires or fails, use a BIN lookup to position Pay by Bank as continuity, and take the customer straight to the specific Pay by Bank method.

Wording, from Key end-user benefits:

Announce and remind through the channels the customer already uses, with the templates for their state. Stop each campaign once the customer has done what it asks.

• New to Pay by Bank: Try Pay by Bank
• Pays one time: Save an account for One Tap
• Legacy journey: Move from the legacy journey

Reinforce completion before any optimisation. State the payment status explicitly, and confirm the payment separately from the balance being available (Payment-status copy).

Show a neutral, human-readable explanation and offer a retry or another way to fund.

If the outcome is not known yet, say so, and do not prompt a new payment:

Recover the intent after an abandoned redirect. Suggest saving the account only when the friction repeats or the behaviour is habitual. Never prompt a new payment while an earlier outcome is pending or unknown.

Recover the intent without punishment. Do not prompt again straight away.

When a saved-account payment fails, subject to the error states available, fall back to a one-time payment with the same bank where possible, so the customer only has to approve and continue.

Tell customers before they reach a configured limit, so a limit never slows down an intent to pay.

Avoid repeated rejection loops: say that the limit is set by the customer’s bank, and how to change it.

Where a saved-account payment is taken as several debits, explain why, so the customer is not surprised by them.

Degrade gracefully, with another way to fund.

Give customers visibility of their saved connection, and control to remove it.

Tell customers in advance when their consent is about to expire, at a moment you know they use the app, to keep momentum. If it expires during a payment, ask them to reconnect.

Wording, from the save-an-account campaign rules:

Design’s draft for the advance notice, awaiting PMM: “Your access to One Tap top-ups will expire soon, let’s reconfirm your controls to keep you going.”

Reinforce changes to the permission: when a connection is saved, about to expire, expired or removed. Use the post-setup and reconnection templates in the save-an-account campaign rules.