Pay by Bank Statuses

When you receive a webhook from Acquired.com the JSON payload will contain a status field which tells you about the current status of the payment.

When Acquired.com delivers a form POST to your redirect_url the status field will also be present.

The table below describes each of these payment statuses:

Status	Description
`cancelled`	The user did not provide consent for the payment to be set up, selecting to reject the payment.
`declined`	The payment request was declined by the bank, or the user failed to authenticate the payment.
`error`	The payment has failed (see detail below).
`expired`	The payment has been abandoned by the user (see detail below).
`executed`	The payment request has been executed by the bank. (If the funds are settled outside of an Acquired.com ledger, the final payment status would stay at executed).
`settled`	The payment has been received into your Acquired.com settlement account. (This status is only applicable for customers that use Acquired-held accounts, where Acquired.com collects the money.)

Error status

What can cause a payment to result in error status?

There are a couple of reasons why a payment could be in an error status:

The originating bank could not send the payment (e.g. because of some internal error).
There is something wrong with the Faster Payments network.

Expired status

What can cause a payment to result in expired status?

Once the user has selected their bank, they have 10 minutes to authorise the payment. If the user does not action the authorisation the status of the payment will resolve to expired. There are different reasons why this would happen:

The user has selected the bank, but abandoned the flow and closed the bank's app/website without selecting the cancel button.
The user has experienced an error whilst being redirected to their banks environment.
The user has failed the authentication process.