Webhooks generated on the plataforma de pagamentos da Adyen share a similar format and are delivered in the same way across sales channels. Platform-generated webhooks inform you asynchronously of transaction details and settings updates.<\/p>\n
There are two types of platform-generated webhooks relevant for in-person payments:<\/p>\n
To add standard or terminal management webhooks, follow our webhooks documentation<\/a> to:<\/p>\n In a point-of-sale integration, standard webhooks may seem less important, because the terminal provides instant feedback: it immediately shows if a transaction is approved or declined. And even if you do not receive the Terminal API response with the transaction details, you can get the details through a transaction status request<\/a>.<\/p>\n However, there are point-of-sale use cases that rely on standard webhooks:<\/p>\n Standard webhooks include a few details by default, as well as configurable additional data. Depending on your use case, you need to and select identifiers<\/a> that you want to receive in the additional data of webhooks.<\/p>\n To configure the structure, when setting up a standard webhook<\/a>:<\/p>\n Select the additional settings<\/a> you want to receive. For example:<\/p>\n\n
Standard webhook<\/h2>\n
\n
\n
\n