Payment states

Understanding what the state field means in Banked's payment session

When you GET a payment session with a payment ID, or when you receive a webhook from Banked the JSON payload will contain a state field which will tell you about the state of the payment.

Payment session

awaiting_providerA Banked payment link has been generated, but the user has not selected a provider
awaiting_payment_consentThe user is in the authorisation process with their bank
pendingThe user's bank has accepted the payment and is processing it. Pending status may be skipped for some payments.
sentThe payment has been sent, the money has left the users account, cannot be recalled and is within the Faster Payments network
failedThe payment has failed, see below

Refund States

awaiting_detailsThe refund has been initiated, but the details of where to send the refund are missing. An automated email has been sent to the end-user from Banked requesting details.
awaiting_paymentThe refund has been initiated and all the details are in place. The merchant needs to authorise the refund transaction before the money can move.
sentThe refund has been successfully sent.
failedThe refund has failed, see below.
externally processedThe refund has been marked as externally processed. This means that the merchant or partner has handled the refund outside of Banked.

What can cause a 'pending' state?

Payments may enter a Pending state when Banked is unable to confirm if a payment has been sent or failed. The pending state is most commonly seen for a brief period of time between the payment being authorised by the user and the bank confirming that the money has left the user’s account, and is not a cause for concern.

If a payment remains in a pending state for a longer period, this could be due to one of the reasons listed below:

  • Payer account requires multi authorisation and one or more of these have not been given. An example of this may be a joint account where not all parties have authorised the payment.
  • The payer’s bank is performing additional security checks on the payment. This is most common with higher or unusual payments and is usually resolved in a couple of hours.
  • A technical error has occurred during the payment process, and Banked are unable to retrieve the status of the payment. This is extremely rare, and Banked support team will be alerted to these, and will manually confirm the payment’s status with the payer’s bank.

How can this status be resolved?

Integrating with Banked webhooks is the best way to be alerted to a payment status change. In most cases, a pending payment will be resolved quickly. If you have an urgent query about a pending payment, or your payment has been in a pending state for longer than 24 hours, please contact [email protected] with your payment ID.

What can cause a 'failed' state?

There are several reasons why a payment could be in a failed state:

  • The originating bank refused to send the payment (e.g. because there are some restrictions on that users account like anti money-laundering)
  • The originating bank cannot send the payment (e.g. because of some internal error)
  • The user's account has insufficient funds
  • The user refused consent during the authorisation flow
  • The account information in the payee field cannot receive payments (e.g. the sort code and account number are invalid or on a bank watch list)
  • There is something wrong with the Faster Payments network

When will my account receive the funds after a 'sent' status?

When a payment enters the sent state it has been accepted into the The Faster Payments network, which processes interbank transfers in the UK; payments sent by Faster Payments 'usually arrive within minutes, although sometimes they can take up to two hours'. The Faster Payments network handles tens of billions of pounds a day.

It's important to note that once the payment is in the sent state it cannot be recalled by the sender and the Faster Payments network has an SLA that 100% of payments that enter its network will arrive at the receiving bank.