Finaro (formerly Credorax)

API Version

Minimum required API version: 1.2.0

The following features require an API version higher than the minimum:

• 3DS 2.0 Internal requires API version 1.3.0

• 3DS 2.0 External requires API version 1.3.0

Payment Methods

The following table lists all supported payment methods.

Currencies

Finaro supports a wide range of currencies. Refer to the Finaro documentation for a complete list of supported currencies.

Features

The following table provides an overview of all supported and non-supported features.

Feature	Supported	Notes
3DS 2.0 External	Yes
3DS 2.0 PaymentsOS-handled	No
3DS 2.0 Provider-handled	No
3DS 2.0 Self-handled	Yes	Supported flow type: Self-handled Flow. For more information, see 3DS 2 Self-handled Flow.
Installments	No
Level 2 and 3 Data	No
Multi-seller Payments	No
Network Tokens	Yes
Payment Facilitator	No
PayU Risk	No
Pre-authorization	Yes
Retrieve Supported Payment Methods	No
Retrieve Supported Plans	No
Statement Soft Descriptor	No
Stored Credentials Flag	Yes
Transaction Processing without CVV	Yes

Requests

The following table lists all supported requests for card-based transactions.

Use the bodybuilder to create a sample request body for each request type.

• Cards
• eWallet

Setup Procedures

The following table lists the setup procedures that are specific to this provider.

Integration Procedures

The following section lists the integration procedures that are specific to this provider.

Integrating Apple Pay

Integrating Apple Pay involves the following:

• Configuring your Apple Developer Account and adding Apple Pay to your checkout page.

• Integrating Apple Pay with your PaymentsOS transaction flows.

Configuring your Apple Developer Account

Proceed as follows:

1. Configure your Apple Developer Account for Apple Pay. For help, see this Configuring your Environment on the Apple developer site. Note that you will be required to upload a CSR (Certificate Signing Request) certificate as part of the configuration procedures.

2. When setting up your account in step 1, you will generate a apple_pay.cer file. You will need this file to decrypt the payload you receive from Apple when requesting a network token, as explain in the steps that follow.

3. Integrate Apple Pay in your checkout page using Apple’s Javascript API, as explained on the Apple developer site.

Now proceed to integrate Apple Pay with PaymentsOS.

Integrating Apple Pay with PaymentsOS

Finaro supports the Apple Pay Decrypted Token Flow. This means that once you’ve requested a network token through Apple Pay, you must first decrypt the payload you receive in order to extract the network token. To do so, use the apple_pay.cer file that was generated when you setup your Apple Pay developer account. Then pass the token to PaymentsOS in the Create Authorization or Create Charge requests.

The following shows a sample request. Notice that you must specify ApplePay as the token provider in the payment_method.token_provider field, and pass the token itself in the payment_method.card_number field. The request will also need to include the network_token_sca_data.cryptogram and network_token_sca_data.eci values received from Apple.

...
{
"payment_method": {
    "source_type": "network_token",
    "type": "untokenized",
    "token_provider": "ApplePay",
    "expiration_date": "22-2030",
    "card_number": "4242424242424242"
  },
"network_token_sca_data": {
    "cryptogram": "US20170163629A1",
    "eci": "05"
  }
}

Integrating Google Pay™

Integrating Google Pay involves the following:

• Adding Google Pay to your checkout page.

• Integrating Google Pay with your PaymentsOS transaction flows.

Adding Google Pay to your Checkout Page

Start by adding Google Pay to your checkout page, as explained in the Google developer documentation. For guidelines that detail how to reference the Google Pay brand within your website, see the brand guidelines published on the Google developer documentation site.

Now proceed to integrate Google Pay with PaymentsOS.

Integrating Google Pay with PaymentsOS

Once you’ve requested a network token through Google Pay, you must first decrypt the payload you receive in order to extract the network token. Then pass the token to PaymentsOS in the Create Authorization or Create Charge requests.

The following shows a sample request. Notice that you must specify GooglePay as the token provider in the payment_method.token_provider field, and pass the token itself in the payment_method.card_number field. The request will also need to include the network_token_sca_data.cryptogram and network_token_sca_data.eci values received from Google.

...
{
"payment_method": {
    "source_type": "network_token",
    "type": "untokenized",
    "token_provider": "GooglePay",
    "expiration_date": "22-2030",
    "card_number": "4242424242424242"
  },
"network_token_sca_data": {
    "cryptogram": "US20170163629A1",
    "eci": "05"
  }
}

Testing

Contact your account manager for test credentials. To download test card data, click here.