The information mentioned in this section must be detailed in the Merchant Onboarding

What we need from you, as a merchant

  1. Base URL of the web site
  2. Store logo URL
  3. Redirection URL for successful payments [optional in widget, with redirection is mandatory].
  4. Redirection URL for failed payments [optional in widget, with redirection is mandatory] [can be the same URL of point 3] [can be the same URL of point 3]
  5. Webhook URL for status update

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> In case of integrating by API and not defining the optional URLs, they will be defined as follows:

</aside>

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> In case of plugin integration it is not necessary to define optional URLs.

</aside>

What ETpay provides you

We will send you the following information, which will be used to start the integration process:

Deliverable Documentation reference
Merchant Code [MERCHANT_CODE]
API Token Password [MERCHANT_API_TOKEN]
Base API URL [API_URL]
Payment funnel URL [PMT_URL]

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> The TNB Integration with API Rest section goes into detail on how to use this information.

</aside>


Back to Non-Banking Cards (TNB)