Service description (Brazil)

• 1. E-commerce implementation

  Merchant may choose to use the Payment Interfaces described below to connect to Adyen's API to submit payment details for Card Not Present Transactions to be processed by Adyen (in each case subject to verification by Adyen of the implementation thereof).

  1. Pay by Link Pay By Link allows Merchant’s customers to submit payment details on an Adyen-hosted page. Merchant has the ability to customize the page by setting made available by Adyen.

  2. Drop-in Drop-in is a full web form to submit payment details, which can be incorporated in its entirety on Merchant’s website or app. It supports multiple payment methods (supported payment methods are listed at https://docs.adyen.com/online-payments/drop-in-web) which can be selected by Merchant and includes the different flows of these payment methods (e.g. redirect, QR code, 3D Secure).

  3. Components The Components integration is similar to the Drop-in integration and supports the same Payment Methods, but can be included on Merchant’s website or app on a per-Payment Method basis.

  4. API only This Payment Interface allows Merchant to send Transaction data directly to Adyen using Adyen’s APIs. This can be used stand-alone or in combination with one of the above. Not using the Drop-in or Components integration for Cards, and thus gathering and submitting unencrypted Card data to the Adyen API, is only permitted with prior approval by Adyen. If Merchant gathers such unencrypted Card data itself, Merchant must be able to demonstrate that its systems are PCI DSS certified at the appropriate level (to be confirmed by Adyen) before using the API only integration for Cards. The last paragraph of Clause 4.2 of the Adyen Terms and Conditions regarding connection to the API interface will apply in such case.

  Merchant may be required to complete a PCI Self-Assessment Questionnaire in accordance with Merchant’s PCI Compliance requirements and Merchant should ensure compliance with the answers provided in such questionnaire.

  In case of the Drop-in or Components integration, iFrames for web and encryption for iOS and Android are used to encrypt the data for some input fields (where required, e.g. for Card data input fields). As a result, no unencrypted Card data from those fields will be visible to Merchant, while retaining full customizability for the remainder of Merchant’s payment page or app. In case of the Pay by Link integration, Merchant will also have no visibility of unencrypted Cardholder data.

• 2. Additional Services for e-commerce

  If any Adyen fees are applicable to an additional Service described below, it will be charged as set out in your Merchant Agreement. Any Interchange Fees or scheme fees charged by the Scheme Owners will be passed through to Merchant.

  • 2.1 Adyen RevenueProtect

    RevenueProtect is the essential risk mitigation service of the Adyen payments platform, at heart a rule-based engine with a configurable scoring component that is supported by a set of advanced transaction linking algorithms and machine learning to optimize risk checks. The features of RevenueProtect provide Merchant with the necessary tools to mitigate fraud and reduce false positives. Adyen RevenueProtect will be charged as agreed in the Merchant Agreement.

  • 2.2 Adyen Authentication Service

    Merchant can opt to use Adyen’s 3D Secure server and SDK to perform transaction authentications with the relevant Scheme Owners (the “Authentication Service”), which includes Adyen’s 3DS 2 solution. Such authentications can be linked to or can be executed independent from a later payment authorization. Merchant can use the Authentication Service with or independently of the Adyen Acquiring Service. Merchant commits to use the Authentication Service in accordance with the provided technical guidance. The Authentication Service will be charged as agreed in the Merchant Agreement.

  • 2.3 Adyen RevenueAccelerate

    RevenueAccelerate is Adyen’s payment optimization service which uses machine learning to optimize the processing of individual transactions. The features of RevenueAccelerate are meant to boost authorization rates, reduce processing costs, improve user experience and reduce churn. RevenueAccelerate also includes the following features:

    • 2.3.1 Account Updater

      The following terms apply for Merchants who start using Account Updater on or after 1 March 2022:

      The Account Updater Service allows Merchant to request and receive updated Payment Details from Adyen and/or the relevant Schemes Owners (where supported by such Scheme Owners and, if applicable, the Issuing Bank for the Card), either real-time or by batch submission.

      Merchant agrees that any updates to Payment Details (e.g. expiry date of a Card) may be used by Adyen to improve or provide payment services on its platform.

      If Merchant chooses to deactivate the Account Updater Service, no additional fees shall accrue; however, this Addendum (including agreed fees) will continue to apply for any Payment Details updates prior to the date of deactivation.

      If Merchant uses Adyen's Account Updater Services, it will be charged as agreed in the Merchant Agreement for each response with Payment Details updates (including a “Contact Cardholder” response).

      Merchant shall comply with Data Protection Laws when requesting the updated Payment Details, which includes relying on a valid legal ground and providing sufficient information to the Cardholder.

      For Merchants who entered into a contract including Account Updater before 1 March 2022, the following terms continue to apply:

      The Account Updater Service allows Merchant to request and receive updated Card information from the relevant Card Schemes (where supported by such Card Scheme and the Issuing Bank for the Card), either real-time or by batch submission.

      If Merchant uses Adyen's Account Updater Services, it will be charged as agreed in the Merchant Agreement for each of the following matched responses: New Account Number, New Expiry Date, Closed Account and (for Visa only:) Contact Cardholder.

    • 2.3.2 Network Token Optimization

      Network Token Optimization uses Network Token technology offered by Scheme Owners. With regards to Network Tokenization, You grant Adyen permission to, on Your behalf, (i) request and retain a Token Requestor ID for each Scheme Owner and (ii) use the Token Requestor ID to provision tokens.

  • 2.4 Network Token Sharing Service

    A “Network Token” is a non-sensitive reference to a shopper’s payment card created by the networks (Scheme Owners). With Network Token Sharing, Adyen can share Network Tokens with its customers (merchants or platforms) for them to store and/or use to process payments with other payment providers.

    By enabling Network Token Sharing, (i) you grant Adyen permission to request and retain a Network Token requestor ID for each Scheme Owner and use the Network Token requestor ID to provision Network Tokens on your behalf, (ii) Network Tokens are provisioned by Adyen and shared with you, and (iii) Network Token lifecycle management will be enabled, meaning that updates of the Network Token (e.g. new PAN or expiry dates, or closed account) are automatically pushed to the merchant or platform by Adyen each time such updates are received by Adyen from the Scheme Owner. 

    In order to process a customer-initiated transaction (CIT) outside of the Adyen environment via another payment service provider, you will need to retrieve a one-time cryptogram from us and share both the Network Token and cryptogram with the third party payment provider. Third party payment providers can then use the Network Token to process a transaction. 

• 3. POS implementation

  If Merchant wishes to use Payment Terminals for submitting POS Transactions, it must use Payment Terminals which are approved by Adyen and which are configured in accordance with the then current configuration requirements and supported versions as specified by Adyen from time to time.

  Merchant can implement its use of the Payment Terminals as follows:

  1. Stand-alone The Payment Terminal is used as a stand-alone device and is not linked to, or integrated with, a third party device such as a cash register or tablet (“POS Device”).

  2. Terminal API Integration Merchant connects an external device or platform to the Payment Terminal via the Adyen Terminal API. More information on the Terminal API Integration is available on docs.adyen.com.

  3. Third party Integration Certain third parties may offer an integration to the Adyen platform with such third party’s solution (e.g. as part of their cash register software). A list of third party solutions with an integration to Adyen is available on request.

• 4. Serviços Adicionais para POS

  • 4.1 SIM subscription for Mobile SIM Payment Terminals

    For Mobile SIM Payment Terminals, Adyen will supply the SIM card together with the Payment Terminal and will remotely (re)activate the SIM card upon Merchant’s request. Upon such (re)activation, Merchant agrees to enter into a SIM subscription period of 12 months, which will be tacitly renewed with consecutive 12 months periods until terminated by Merchant notifying Adyen Support at least one month in advance of the end of the relevant subscription period. Upon such termination, the SIM card will be deactivated (and can be reactivated in accordance with the foregoing).

    The monthly subscription fee as agreed in the Merchant Agreement will apply for activated SIM cards. Mobile SIM Payment Terminals can only be used with SIM cards that are supplied by Adyen. Upon termination of this Merchant Agreement, all Merchant’s SIM cards will be automatically deactivated and must be returned by Merchant together with the Payment Terminals as set out in the Merchant Agreement.

  • 4.2 Autorização offline, MKE e MOTO

    • 4.2.1 x

    • 4.2.2 x

    • 4.2.3 x