Statuses

When you receive a webhook from Acquired.com the JSON payload will contain a status field which tells you about the current state of the payment or mandate. For one-off payments, the status field is also present when Acquired.com delivers a form POST to your redirect_url.

One-off payment statuses

Status	Description
`cancelled`	The customer did not provide consent for the payment, selecting to reject it.
`declined`	The payment request was declined by the bank, or the customer failed to authenticate.
`error`	The payment failed due to a technical issue (see detail below).
`expired`	The payment was abandoned by the customer (see detail below).
`executed`	The payment request has been executed by the bank. If funds are settling outside of an Acquired.com ledger, the final payment status will remain at `executed`.
`settled`	The payment has been received into your Acquired.com settlement account. This status only applies to merchants using Acquired-held accounts.

Error status

An error status indicates the payment failed due to a technical issue — either at the originating bank or on the Faster Payments network.

Expired status

Customers have 10 minutes to authorise a payment after selecting their bank. If they don't complete authorisation within this window (e.g. they abandon the flow, encounter a redirect error, or fail authentication), the payment resolves to expired.

The customer failed the authentication process at their bank.

Mandate statuses

The following statuses apply to VRP mandates, which govern the authorisation a customer grants for recurring Open Banking payments.

Status	Description
`pending`	The mandate has been created and is awaiting customer authorisation.
`active`	The customer has authorised the mandate. Payments can now be collected within the agreed constraints.
`cancelled`	The mandate has been cancelled, either by the customer directly from their banking app or by the merchant via the API. No further payments can be collected.
`expired`	The mandate's validity period has ended (i.e. the `end_date` constraint has passed). No further payments can be collected.
`failed`	The customer's authorisation attempt was unsuccessful, or the mandate could not be created.

Mandate lifecycle

A mandate transitions through two phases. During setup, a pending mandate will move to activated if the customer authorises successfully, or to failed or expired if authorisation is unsuccessful or not completed in time. Once activated, a mandate remains active until it is either cancelled by the customer or merchant, or expired when the end_date passes.

Note: Customers can cancel a mandate at any time directly from their banking app, and merchants can cancel mandates via the Acquired-hosted flow. You will receive a webhook notification when either occurs. Ensure your integration handles cancelled mandate webhooks to prevent attempting payments against an inactive mandate.

VRP payment statuses

The following statuses apply to individual payments collected against an active VRP mandate. Unlike one-off payments, VRP payments do not require a customer redirect, so there is no redirect_url form POST for these.

VRP payment statuses share several values with one-off payments but do not include cancelled or expired, as VRP payments do not involve a customer flow.

Status	Description
`pending`	The payment has been initiated and is being processed.
`executed`	The payment has been executed by the bank. If funds are settling outside of an Acquired.com ledger, the final payment status will remain at `executed`.
`settled`	The payment has been received into your Acquired.com settlement account. This status only applies to merchants using Acquired-held accounts.
`declined`	The payment was declined. This may occur if the payment exceeds the mandate constraints, or if the bank declined execution.
`error`	The payment failed due to a technical issue (see detail below).

Note: Always validate that a payment amount falls within the mandate's max_amount_per_payment and periodic_limit constraints before initiating a payment. Payments that exceed these limits will be declined.

Error status

An error status indicates the payment failed due to a technical issue — either at the originating bank, on the Faster Payments network, or because the mandate was no longer active at the time of the attempt.