Confirmations

Review, slide, confirm.

Money never settles on a tap. Every payment passes through three steps, and only the last one, your confirmation, lets it go.

  • The review shows what leaves your account and what arrives.
  • The slide creates the payment. Nothing moves yet.
  • Your confirmation settles it.
  • Asking for a new code does not add time.
The confirmation step of a payment: six boxes for the code, a Send it again button with the note that sending it again does not give you more time, and the Confirm button
The review step of Send: who is paid, the currency they are paid in, the account it leaves from, the rail and the amount

Three steps, every time

  1. Review

    Before anything happens, the review lays out the payment: who receives it, which account it leaves, what you pay and what they receive. If something is wrong, go back and change it. Nothing has been created yet.

  2. Slide

    “Slide to send” creates the payment and holds it, waiting for you. The money is still in your account. Sliding is a deliberate gesture, so a tap alone never settles a payment.

  3. Confirm

    The app asks you to confirm it is you: with a passkey on this device, the current code from your authenticator app, or a confirmation code. Only then does the payment go. If the window closes before you finish, nothing is sent.

When a code is wrong

Too many wrong codes close the payment.

A wrong code is refused on the spot, and you can try again. Past a set number of tries the screen says “Too many attempts”: the confirmation is closed, the payment fails and nothing was sent. The money never left your account, and you start again with a new payment.

The Confirm it is you sheet after too many wrong codes: the confirmation is closed, nothing was sent, and a Start again button

Also confirmed

Cancelling a standing order asks you first. Pausing does not.

A standing order converts money as it arrives. Pause stops it until you resume, with no confirmation, because nothing is lost by waiting. Cancel ends it for good, so it is confirmed like a payment. Money already moved stays where it is.

The details of an active standing order that converts money on arrival and sends it on, with the conversions it has made, a Pause button and Cancel this order

Also confirmed

Trusting a payee is confirmed too.

People you pay lists your saved destinations and whether you trust each one. Marking one as trusted is confirmed the same way a payment is. A standing order can send money on only to a destination you trust, and a trusted destination has to stop being trusted before it can be removed.

A saved payee’s bank account, marked not trusted, with buttons to add it to favourites, to trust it and to remove it

Also confirmed

Removing a way to confirm is confirmed as well.

Taking away a passkey or an authenticator app is confirmed like a payment, because it guards every payment after it. The last one cannot be removed at all: the screen says it is the only way left to confirm a payment.

The Security settings: a passkey with its Remove button, and the note that removing a way of confirming payments is itself confirmed, like a payment

Questions about confirmations

What happens after wrong codes?

The confirmation closes and the payment fails. Nothing was sent, so the money is still in your account. Start a new payment when you are ready.

Does a new code give me more time?

No. You can ask for the code again, but the window to confirm does not start over. The screen says so plainly: sending it again does not give you more time.

What can I confirm with?

A passkey on your device, the current code from an authenticator app, or a confirmation code. The confirmation screen says which one it is asking for. You manage passkeys and authenticator apps in Settings, under Security.

Does pausing a standing order need a confirmation?

No. Pausing and resuming ask for no confirmation, because nothing is lost by waiting. Cancelling is different: it ends the order for good, so it asks you to confirm first.