{"title":"Scheme advice","category":"default","creationDate":1786532071,"content":"

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.<\/p>\n

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.<\/p>\n

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.<\/p>\n

Get updates<\/h2>\n

To get real-time updates about the status changes because of the scheme's advice, you can use the following methods:<\/p>\n

1. Transfer webhooks<\/h3>\n

When Adyen updates the status of a payment based on the scheme's advice, you receive an additional balancePlatform.transfer.updated<\/a> webhook with a new event for the updated booking. You can identify webhooks related to scheme advice by the following fields:<\/p>\n\n\n\n\n\n\n\n
Field<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
data.reason<\/code><\/td>\nReturns schemeAdvice<\/strong><\/td>\n<\/tr>\n
data.status<\/code><\/td>\nReturns authorised<\/strong> or refused<\/strong><\/td>\n<\/tr>\n
data.events<\/code><\/td>\nReturns a new event for the updated booking based on the scheme's advice. This event has the status adviceAuthorised<\/strong> or adviceRefused<\/strong>, and determines whether the general status of the payment (returned in data.status<\/code>) is authorised<\/strong> or refused<\/strong>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

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.<\/p>\n

\n \n
\n
\n <\/i>\n
\n

Example webhooks<\/h4>\n <\/div>\n <\/div>\n
\n \n

In the following example:<\/p>\n

    \n
  1. Adyen originally refuses the payment during the initial authorization flow.<\/li>\n
  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.<\/li>\n<\/ol>\n

    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<\/a>.<\/p>\n

      \n
    1. \n

      Adyen originally refuses the payment during the initial authorization flow.<\/p>\n

      \n<\/code-sample>\n<\/div>\n<\/li>\n
    2. \n

      Adyen updates the payment based on the scheme's advice.<\/p>\n

      \n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\n\n <\/div>\n <\/div>\n<\/div>\n\n

      2. Customer Area<\/h3>\n

      In the Customer Area, you can view details about the payments made with your issued cards<\/a> by navigating to Balances<\/strong> > Transfers<\/strong>. By clicking on a specific payment, you can find the details about its status and past status changes under Transfer lifecycle<\/strong>.<\/p>\n

      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<\/strong> or AdviceRefused<\/strong>, and is reflected in the Transfer lifecycle<\/strong>. These statuses reflect the scheme's final decision on the payment, and determine the final balance change.<\/p>\n

      Reconcile payments<\/h2>\n

      To reconcile payments that have been updated based on the scheme's advice, you can use the Balance Platform Account Report (BPAR)<\/a>. This report provides a detailed overview of the payments made with your issued cards.<\/p>\n

      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:<\/p>\n

        \n
      1. The Description<\/strong> column is populated with the following value: schemeAdvice<\/strong>.<\/li>\n
      2. The Status<\/strong> column records the final decision on the payment by the scheme: authorised<\/strong> or refused<\/strong>.<\/li>\n<\/ol>\n

        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<\/strong> column for these events differ, then the row with Description<\/strong> set to schemeAdvice<\/strong> determines the final change to the reserved balance.<\/p>\n

        Here is an example of the BPAR booking when both Adyen and the scheme authorizes a payment:<\/p>\n\n\n\n\n\n\n\n
        Category<\/th>\nType<\/th>\nStatus<\/th>\nPayment Currency<\/th>\nReserved (PC)<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
        issuedCard<\/td>\nPayment<\/td>\nreceived<\/td>\nUSD<\/td>\n0<\/td>\n<\/td>\n<\/tr>\n
        issuedCard<\/td>\nPayment<\/td>\nauthorised<\/td>\nUSD<\/td>\n-40<\/td>\n<\/td>\n<\/tr>\n
        issuedCard<\/td>\nPayment<\/td>\nauthorised<\/td>\nUSD<\/td>\n0<\/td>\nschemeAdvice<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

        Here is an example of the BPAR booking when Adyen refuses a payment and the scheme authorizes it:<\/p>\n\n\n\n\n\n\n\n
        Category<\/th>\nType<\/th>\nStatus<\/th>\nPayment Currency<\/th>\nReserved (PC)<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
        issuedCard<\/td>\nPayment<\/td>\nreceived<\/td>\nUSD<\/td>\n0<\/td>\n<\/td>\n<\/tr>\n
        issuedCard<\/td>\nPayment<\/td>\nauthorised<\/td>\nUSD<\/td>\n0<\/td>\n<\/td>\n<\/tr>\n
        issuedCard<\/td>\nPayment<\/td>\nauthorised<\/td>\nUSD<\/td>\n-40<\/td>\nschemeAdvice<\/td>\n<\/tr>\n<\/tbody>\n<\/table>","url":"https:\/\/docs.adyen.com\/issuing\/authorisation\/scheme-advice","articleFields":{"description":"Replace this string with a content string that appears below the title","feedback_component":true,"filters_component":false},"algolia":{"url":"https:\/\/docs.adyen.com\/issuing\/authorisation\/scheme-advice","title":"Scheme advice","content":"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.\nAfter 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.\nIf 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.\nGet updates\nTo get real-time updates about the status changes because of the scheme's advice, you can use the following methods:\n1. Transfer webhooks\nWhen Adyen updates the status of a payment based on the scheme's advice, you receive an additional balancePlatform.transfer.updated webhook with a new event for the updated booking. You can identify webhooks related to scheme advice by the following fields:\n\n\n\nField\nDescription\n\n\n\n\ndata.reason\nReturns schemeAdvice\n\n\ndata.status\nReturns authorised or refused\n\n\ndata.events\nReturns 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.\n\n\n\nThe 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.\n\n \n \n \n \n \n Example webhooks\n \n \n \n \nIn the following example:\n\nAdyen originally refuses the payment during the initial authorization flow.\nThe 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.\n\nBelow 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.\n\n\nAdyen originally refuses the payment during the initial authorization flow.\n\n\n\n\n\nAdyen updates the payment based on the scheme's advice.\n\n\n\n\n\n\n \n \n\n\n2. Customer Area\nIn the Customer Area, you can view details about the payments made with your issued cards 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.\nWhen 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.\nReconcile payments\nTo reconcile payments that have been updated based on the scheme's advice, you can use the Balance Platform Account Report (BPAR). This report provides a detailed overview of the payments made with your issued cards.\nWhen 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:\n\nThe Description column is populated with the following value: schemeAdvice.\nThe Status column records the final decision on the payment by the scheme: authorised or refused.\n\nEvents 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.\nHere is an example of the BPAR booking when both Adyen and the scheme authorizes a payment:\n\n\n\nCategory\nType\nStatus\nPayment Currency\nReserved (PC)\nDescription\n\n\n\n\nissuedCard\nPayment\nreceived\nUSD\n0\n\n\n\nissuedCard\nPayment\nauthorised\nUSD\n-40\n\n\n\nissuedCard\nPayment\nauthorised\nUSD\n0\nschemeAdvice\n\n\n\nHere is an example of the BPAR booking when Adyen refuses a payment and the scheme authorizes it:\n\n\n\nCategory\nType\nStatus\nPayment Currency\nReserved (PC)\nDescription\n\n\n\n\nissuedCard\nPayment\nreceived\nUSD\n0\n\n\n\nissuedCard\nPayment\nauthorised\nUSD\n0\n\n\n\nissuedCard\nPayment\nauthorised\nUSD\n-40\nschemeAdvice\n\n\n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Adyen Issuing","lvl2":"Payment authorisation","lvl3":"Scheme advice"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/issuing","lvl2":"https:\/\/docs.adyen.com\/issuing\/authorisation","lvl3":"\/issuing\/authorisation\/scheme-advice"},"levels":4,"category":"Issuing","category_color":"green","tags":["Scheme","advice"]}}