Payment Provider Framework (PPF) is an alternative way to develop payment connectors for your integration through VTEX IO. Since the development is based on a boilerplate of an IO app, a lot of the work is already done to implement the needed feature including the API routes, the types used in the request and response bodies, and the Secure Proxy. With PPF, developers also do not need to worry about hosting the connector since it is hosted on the IO infrastructure.

To develop a new payment connector, it is mandatory to follow the prerequisites determined by VTEX. You can learn about them in the Implementation prerequisites section of our Payment Provider Protocol article.

If you're starting a brand new project, we recommend you to clone the example repository, as it already has all the basic configuration setup.

Once you have the repository code in your workspace, you have to make sure you have all the necessary dependencies and that they are updated. To do so, follow these steps:

1. Run the following command on your node folder:

2. Go to your package.json and make sure it has been added as a dependency with the correct version:

3. Check in the package.json the version of @vtex/api, which should be listed in the devDependencies as follows:

4. When linking your app, this version might get updated to a later than 6.x version, which is fine. In case it is not listed as a devDependency, run the following command on your node folder:

If you get any type errors or conflicts in your project related to @vtex/api, follow these steps to resolve the problem: delete the node_modules folder and the yarn.lock file from both your project root and your project's node folder, then run the command yarn install -f in both folders.

5. In your manifest.json, you should check the builders section, in which you must include the paymentProvider in its current version. This will add policies to callback the Payment Gateway APIs and also expose Payment Provider protocol routes.

In order to create your service, you must implement your payment provider connector and the service itself. To help you with them, we have the following sections.

This is an abstract class with the signatures of the route functions required in your connector, according to the protocol.

You must create a new class extending the Payment Provider, which must implement a function for each route. The functions will receive the request body (when there is one) as a parameter and the response must be returned as an object, such as the example shown below:

Typescript should automatically check for typing errors, but if you need, you can check the requests and responses signatures from the Payment Flow endpoints in our API Reference.

To specify which payment methods the connector will accept to process:

1. Create a folder named paymentProvider using the following folder structure:

2. Then, inside the paymentProvider folder you must create a file named configuration.json.

3. Declare the accepted payment methods, for instance:

By doing this you do not need to declare the /manifest route. They will be implemented automatically by the builder.

The name field indicating the name of the connector must be replaced with the name of your provider. This field cannot be filled with a value "MyConnector".

The available payment methods can be found in the Admin, by going to the left panel and accessing Transactions > Payments > Payment conditions, then clicking on the green plus (+) button as if you were adding a new payment option. Check more details on the Configuring payment conditions article. In case you want to support a new payment method that is not available, you need to open a ticket to the VTEX team informing them of this new payment method.

Generally speaking, the manifest route makes no difference at runtime. If you have a use case to override the default route, open a ticket to the VTEX support team. But, if you want to override it any way you have to add special parameters to it.

Pay attention to x-provider-app. It should be updated every time that your major changes.

Example: The x-provider-app header should have a value of vtex.payment-provider-example@1.2.3

You can also omit the handler and headers parameters, by doing it you will need to implement it on your own.

Along with manifest fields (paymentMethods and customFields) there are the following configurable options.

Parameter name	Required	Default	Description
name	Yes		Name of connector.
serviceUrl	Yes	Auto-generated for IO connectors.	A valid URL (can include relative paths).
implementsOAuth	No	false	Defines if the provider implements or not the configuration flow supporting OAuth authentication.
implementsSplit	No	false	Defines if the provider implements or not the split flow.
usesProviderHeadersName	No	true	Defines if the provider will receive appKey and appToken headers as "x-provider-api-appKey" and "x-provider-api-appToken" respectively.
useAntifraud	No	false	Defines if the provider can or cannot be used along antifraud providers.
usesBankInvoiceEnglishName	No	false	Defines if the Bank Invoice payment method will use the English name, if true, or the Brazilian name (Boleto Bancário), if false.
usesSecureProxy	No	true	If true, the provider can process payment without being PCI-Certified, the connector will receive a secureProxyUrl on createPayment flow, and the card encrypted data. If false, the provider must be a PCI-Certified entity, and you should send the AOC containing the provided serviceUrl.
requiresDocument	No	false	If true, the customer must include the cardholder document on Checkout. A new field will appear on the Checkout form. If false, the customer does not need to include a cardholder document.
acceptSplitPartialRefund	No	false	If true, a partial refund will be sent when a payment split occurs. If false, the connector couldn't process a partial refund when a payment split occurs.
usesAutoSettleOptions	No	false	If true, the client will be able to choose the behavior of the auto settlement in the VTEX admin configurations of the provider. The options available are the following: Use behavior recommended by the payment processor, Automatic capture immediately after payment authorization, Automatic capture immediately after anti-fraud analysis, Deactivated: Not automatically captured. If false, the connector won't have this dropdown configuration field for auto settlement. More information can be found in the Custom Auto Capture Feature article.

A retry is required to develop your connector according to the protocol, so we built a function, which can be invoked as shown below:

More information about the retry flow can be found in the Payment Authorization section of the Payment Provider Protocol article.

This is a class that extends the Service from @vtex/api. You must invoke it by passing the developed connector as a property of the first parameter and it will automatically set up the required routes for you. The following code shows how to do it and is found in the node/index.ts file.

By default, the Payment Provider Service declares the following routes:

• /manifest
• /payments
• /settlements
• /refunds
• /cancellations
• /inbounds

If your service requires any extra routes, you must declare them separately and use them as parameters:

If your connector requires any extra clients, you must also pass them in the parameters along with the connector:

For processing credit, debit or co-branded card transactions, integrations must be compliant with PCI-DSS security standards. For integrations hosted in VTEX IO supporting one of those payment methods, it is mandatory to use Secure Proxy to make calls to a PCI-certified endpoint. You can check more details in the Secure Proxy article.

The endpoint must be allowed by VTEX Secure Proxy. This must be requested via ticket sending the AOC with the wanted endpoint. Currently the Secure Proxy only accepts two Content-Types: You can use \"application/json\" or \"application/x-www-form-urlencoded\". Any other Content-Type will not be supported.

To make calls over our Secure Proxy, you must:

1. Extend the SecureExternalClient abstract class. The constructor of the class is made in a way that VTEX allows 'http://my-pci-certified-domain.com' as one of the trusted destinations by receiving its AOC.
2. Set the Secure Proxy URL on the request that you want to be proxied. SecureProxyURL is received on createPayment flow.

Now that you have a new connector ready to be used, you can test it entirely in the production flow using your store's Checkout.

The account must be allowed to test IO Connectors. This must be requested via ticket informing the name of the app and the account where the tests will be made.

A prerequisite for this procedure is to have products for sale at your store for testing. To place an order with your new connector:

1. Launch a beta version of your connector. E.g.: vtex.payment-provider-test@0.1.0-beta. If you need, check the Making your app publicly available article to learn how to create a beta version of your app.
2. Install the beta version on master workspace. Wait for around 1 hour.
3. Go to https://{account}.myvtex.com/admin/pci-gateway/#/affiliations/{connector-name}/. Replace {account} for the name of the account you want to test on and {connector-name} for the name of your connector. The format of the name is: ${vendor}-${appName}-${appMajor} (e.g.: vtex-payment-provider-example-v1).
   
4. Change the toggle option to Test.
5. Click on Save and refresh the page.
6. Enter again in the saved configuration and you will notice that a new field appears, called Workspace.
7. Set the Workspace as you wish. You can leave it as master if it is the workspace you want to test on.
   
8. Configure a payment condition with your newly created connector and wait 10 minutes to appear on Checkout.
9. Make a purchase with the payment condition you configured with your connector.

Our Payment Provider Test Suite, an app used to test payment connector flows, is not prepared to test cases considering an integration using Secure Proxy. More details about this app can be found in the Payment Provider Homologation article.

Also, differently from connectors that do not use Payment Provider Framework, integrations that do use it do not support the ability to have a sandbox service provider endpoint, which is used for tests. A PPF connector only supports one production endpoint, so the toggle to choose between test and production in the configuration page of the Admin will not appear.

To process sales with your connector on all VTEX accounts, make sure to send the billingOptions field indicated as free in the manifest. If you only want to make it available for some specific accounts, inform our Payments team through a support ticket and do not send the billingOptions field in the manifest. More information about this field can be found in the Billing Options article.

The publication process is made via the app store. More info on how to do that can be found in the Submitting your app to the VTEX App Store article.

After that, you need to open a ticket to the VTEX support team informing them that the integration was completed. However, before opening the ticket, make sure you have the following information:

• Connector App Name: Name of the PPF connector app. Use the following format: "vendor.appname". For example: partnername.connector-partnername. These can be found in the manifest.json file.
• Partner contact: partner email address in case we need to communicate changes and new features of our protocol.
• Production Service Provider Endpoint: the base path that will be used for API calls to the provider, e.g. https://vtex.pagseguro.com. It has to respond to the route {{serviceUrl}}/manifest . This endpoint must be publicly available.
• Allowed Accounts: describe which VTEX accounts from this provider will be available (all accounts or specific accounts).
• New Payment methods: inform if this connector supports a payment method that is not yet available in the VTEX Admin.
• New Payment method purchase flow: if a "New Payment method" is supported, inform whether it works with Redirect or Payment App. For more information, access the Purchase Flows article.

The SLA required for the payment team to carry out homologation is 30 days.

After the homologation step is complete, your app needs to be installed in the account that wants to use it. Then, a new affiliation will be available to configure it.