Help us improve our documentation! Tell us about your experience with this article by completing this form.

Anti-fraud solutions play a crucial role in ensuring secure payment transactions by performing risk analysis. VTEX offers integration capabilities for anti-fraud systems through the Anti-fraud Provider Protocol. This protocol is an agreement between VTEX and providers, defining a set of rules that have to be implemented by the providers in their integrations. The integrations must include a set of endpoints defined in our Anti-fraud Provider Protocol API.

On VTEX, gift cards are treated as a payment option, and their transactions are processed at Checkout. Besides our native solution, VTEX allows external gift card providers to implement integrations using our Gift Card Provider Protocol. Through this protocol, providers can develop a middleware containing the endpoints described in our Gift Card Provider Protocol API and connects with our Gift Card Hub. You can check more details about gift cards in the articles below:

• Gift Card introduction
• Gift Card system architecture
• Gift Card Provider Protocol API

VTEX's payment systems offer extensive resources to support various payment methods, conditions, and integrations. This versatility also comes with complexity. If you are developing an integration or dealing with a more complex payment configuration, a better understanding of VTEX Payments architecture might help you. See more details in these articles:

• Payments introduction
• Payment Methods
• Purchase Flows

The most common process for enabling payments in your store is by configuring an affiliation related to the provider you have a contract with and a payment method in the Admin. Instructions for this process can be found primarily in our Help Center. However, some configurations are more advanced and are described in the articles below:

• Setting up Merchant ID in Apple Pay
• Installing Affirm Payment App

When adding or editing a payment configuration in your store, you might need specific use cases, such as defining a type of interest rate or processing payments through an external seller. Read the articles below for more information:

• Setting up the type of interest rate
• External seller processing payments

Payment providers can implement their integrations using our Payment Provider Protocol. This protocol enables providers to create a payment connector that interacts with our Gateway and contains the endpoints described in our Payment Provider Protocol API. Besides developing the connector, providers must also test them and ensure they follow the required security standards before they can be available to the stores. Learn more in the articles below:

• Payment Provider Protocol
• Payment Provider Protocol API
• Implementing a Payment Provider
• Payment Provider Homologation
• PCI - DSS Compliance
• Secure Proxy
• Payment Provider Framework
• Payment Provider Protocol applied to payments with POS

Here are the steps you usually need to follow to implement an integration:

1. If your integration supports credit, debit, or co-branded cards, it's essential to ensure that your payment connector meets one of the following conditions:
   • The connector is hosted in a secure environment that adheres to the PCI - DSS security standards. In this case, an Attestation of Compliance (AOC) is required.
   • The connector is developed using Secure Proxy, where it receives tokens instead of sensitive data related to the card transaction. The Gateway acts as a proxy to communicate with the acquirer.
2. Implement your payment connector based on our Payment Provider Protocol, which includes all the required endpoints. Make sure to list all the payment methods supported by your integration in the response of the List Payment Provider Manifest endpoint. Additionally, for each payment method, you need to implement specific behavior for the Create Payment endpoint.
3. Install your connector in a store and proceed with the homologation step. During this phase, you will test each endpoint of your connector using the Payment Provider Test Suite app.
4. Once your connector successfully passes all the tests, open a ticket, so our team can carry out the homologation process.

When developing a payment integration, you might need to add specific features. You can enable specific payment methods that require additional work (i.e., Pix, an offline payment method in Brazil), create a custom flow or add a validation step in the Checkout (Payment App), among other options. See our available options in the articles below:

• Payment app
• Pix: Instant Payments in Brazil
• Split Payouts on Payment Provider Protocol
• Custom Auto Capture Feature
• Cardholder document configuration
• Layout Development Guide for payment methods in Smart Checkout VTEX