Treezor Documentation

X-Pay is the process of tokenizing an existing card and storing it in a digital wallet (e.g., Apple Pay or Google Pay). This replaces sensitive card information with a Device Primary Account Number (DPAN), allowing wallet providers to process payments without holding the original Primary Account Number (PAN).

Key constraints and requirements:

• A card can have a maximum of 10 active or suspended digitizations.
• The 'Online' option of the issued card must be activated for digitization to work.
• Digitized cards can be temporarily or permanently disabled via the Treezor API.
• Integration and certification with Apple Pay and Google Pay are independent of Treezor and must be handled by the developer directly with the wallet providers.

Advanced capture allows you to authorize a specific amount on a tokenized third-party card and then capture those funds later. This is useful when the final capture amount is unknown at the time of authorization.

Key constraints:

• Authorized funds must be captured within 7 days; otherwise, remaining funds are automatically freed.
• You can create one or more payins against a single authorization, provided the total does not exceed the authorized amount.
• This feature is only available for specific payment products.

Prerequisites:

1. Tokenize the card.
2. Create a Topup Card to associate the card with a user (if required).

Treezor uses Mutual Transport Layer Security (mTLS) to secure sensitive payment card data (PAN, PIN, CVV) in compliance with PCI DSS. This protocol ensures mutual authentication and encrypted communication for all PCI DSS endpoints. All requests must be sent to the following environment-specific URLs:

• Sandbox: https://<your_company_name>.preprod.secure.treezor.co
• Production: https://<your_company_name>.secure.treezor.co

Open Banking Payment Initiation allows merchants to collect payments directly from customers' bank accounts using the Payment Initiation Service Provider (PISP) framework, bypassing card networks. The flow involves redirecting a customer to a secure checkout page to select their bank and authenticate via Strong Customer Authentication (SCA).

Availability: This feature is not enabled by default and is only available on the Connect plan. Contact Treezor to enable it.

Live verification allows remote identity verification via live video to mitigate fraud. Treezor offers two mutually exclusive methods; you must contact Treezor to enable one of them:

• Liveness: Requires a video of the user, their identity proof, and a SEPA transfer into their Treezor Wallet as an extra validation step.
• Certified video (PVID): An ANSSI-certified method requiring a video of the user and identity proof with interactive challenges, removing the need for extra validation steps.

Both methods use the same API endpoint. The KYC interface (colors, logo, redirection URL) can be customized by contacting Treezor.

Treezor uses the Twig 3.x templating engine to allow developers to customize API outputs. Templates must be base64-encoded when uploaded.

Implementation Constraints:

• Layouts and Blocks are not supported.
• Variables are limited to those explicitly provided by Treezor for a specific template.
• CSS styling must be inlined (e.g., <a style="color:orange;">) or placed within a <style> tag in the <head> of the page.

Scheduled Payment orders allow you to plan a payment execution in the future for either a unique operation or recurring ones. This feature supports both Payouts (SCTE) and Wallet-to-Wallet Transfers.

Workflow:

1. Create a Scheduled Payment order with specific settings (type, dates, etc.).
2. The Transfer or Payout is executed on the scheduled date(s).

Important Notes:

• If a payment execution fails, the occurrence is cancelled and details are added to the failedPayment attribute of the Scheduled Payment object. The end user must then complete the payment manually.
• This is currently a Beta feature; contact your Treezor Account Manager for access.