---
title: "Scheme advice"
description: "Replace this string with a content string that appears below the title"
url: "https://docs.adyen.com/issuing/authorisation/scheme-advice"
source_url: "https://docs.adyen.com/issuing/authorisation/scheme-advice.md"
canonical: "https://docs.adyen.com/issuing/authorisation/scheme-advice"
last_modified: "2026-08-12T12:54:31+02:00"
language: "en"
---

# Scheme advice

Replace this string with a content string that appears below the title

[View source](/issuing/authorisation/scheme-advice.md)

In some cases, the payment scheme steps in to evaluate a payment after Adyen's initial authorization flow. For example, this can happen when Adyen cannot complete the authorization flow in real time.

After performing its own validations, the scheme determines whether to authorize or refuse the payment, and shares this outcome with Adyen. Adyen then updates the payment with a new status that reflects the scheme's advice.

If the scheme's advice differs from Adyen's initial authorization decision, Adyen always defers to the scheme's advice. The scheme's decision determines the final status of the payment and whether the funds are reserved or released. Any decisions made by Adyen after the scheme's decision can create a new event booking, but will not contain any balance changes, nor affect the final status of the payment.

## Get updates

To get real-time updates about the status changes because of the scheme's advice, you can use the following methods:

### 1. Transfer webhooks

When Adyen updates the status of a payment based on the scheme's advice, you receive an additional [balancePlatform.transfer.updated](https://docs.adyen.com/api-explorer/transfer-webhooks/latest/post/balancePlatform.transfer.updated) webhook with a new event for the updated booking. You can identify webhooks related to scheme advice by the following fields:

| Field         | Description                                                                                                                                                                                                                                                           |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `data.reason` | Returns **schemeAdvice**                                                                                                                                                                                                                                              |
| `data.status` | Returns **authorised** or **refused**                                                                                                                                                                                                                                 |
| `data.events` | Returns a new event for the updated booking based on the scheme's advice. This event has the status **adviceAuthorised** or **adviceRefused**, and determines whether the general status of the payment (returned in `data.status`) is **authorised** or **refused**. |

The scheme's decision determines the final status of the payment and whether the funds are reserved or released. When you receive a webhook related to scheme advice, use its status as the final outcome of that payment.

**

#### Example webhooks

In the following example:

1. Adyen originally refuses the payment during the initial authorization flow.
2. The scheme steps in to provide Adyen with the advice to authorize the payment. Adyen defers to the scheme's advice and updates the payment's status and the reserved balance.

Below are the webhooks you receive during this process. Note that these are shortened webhook examples highlighting affected fields. To view the complete webhook, see [Payment advice authorised or refused](/issuing/webhook-types/payment-events#advice-authorized-refused).

1. Adyen originally refuses the payment during the initial authorization flow.

   **Original refusal webhook**

   ```json
   {
       "data": {
         "id": "3RX9ER5XEXH6T3CQ",
         "status": "refused",
         "reason": "unknown"
       },
       "type": "balancePlatform.transfer.updated"
   }
   ```

2. Adyen updates the payment based on the scheme's advice.

   **Update based on scheme's advice**

   ```json
   {
       "data": {
         "id": "3RX9ER5XEXH6T3CQ",
         "status": "authorised",
         "reason": "schemeAdvice",
         "events": [
           {
             "status": "refused"
           },
           {
             "status": "adviceAuthorised"
           }
         ]
       },
       "type": "balancePlatform.transfer.updated"
   }
   ```

### 2. Customer Area

In the Customer Area, you can [view details about the payments made with your issued cards](/issuing/payment-stages/check-details-payment) by navigating to **Balances** > **Transfers**. By clicking on a specific payment, you can find the details about its status and past status changes under **Transfer lifecycle**.

When Adyen receives scheme advice on a payment after the initial authorization flow, we update the payment's status and the reserved balance based on the advice. The new status is set to **AdviceAuthorised** or **AdviceRefused**, and is reflected in the **Transfer lifecycle**. These statuses reflect the scheme's final decision on the payment, and determine the final balance change.

## Reconcile payments

To reconcile payments that have been updated based on the scheme's advice, you can use the [Balance Platform Account Report (BPAR)](/issuing/report-types/balance-platform-accounting-report). This report provides a detailed overview of the payments made with your issued cards.

When Adyen updates a payment based on the scheme's advice, the Balance Platform Accounting Report includes an additional payment event. You can identify such events by the following values:

1. The **Description** column is populated with the following value: **schemeAdvice**.
2. The **Status** column records the final decision on the payment by the scheme: **authorised** or **refused**.

Events related to scheme advice are always additive. A payment can have an event with Adyen's original decision, and an additional event based on the scheme's advice. If the values in the **Status** column for these events differ, then the row with **Description** set to **schemeAdvice** determines the final change to the reserved balance.

Here is an example of the BPAR booking when both Adyen and the scheme authorizes a payment:

| Category   | Type    | Status     | Payment Currency | Reserved (PC) | Description  |
| ---------- | ------- | ---------- | ---------------- | ------------- | ------------ |
| issuedCard | Payment | received   | USD              | 0             |              |
| issuedCard | Payment | authorised | USD              | -40           |              |
| issuedCard | Payment | authorised | USD              | 0             | schemeAdvice |

Here is an example of the BPAR booking when Adyen refuses a payment and the scheme authorizes it:

| Category   | Type    | Status     | Payment Currency | Reserved (PC) | Description  |
| ---------- | ------- | ---------- | ---------------- | ------------- | ------------ |
| issuedCard | Payment | received   | USD              | 0             |              |
| issuedCard | Payment | authorised | USD              | 0             |              |
| issuedCard | Payment | authorised | USD              | -40           | schemeAdvice |