Finaro (formerly Credorax)

Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications in this section to integrate with Finaro.

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.

Payment MethodPayment Method Type
American ExpressCards
Apple Pay - Decrypted TokeneWallet
Google PayeWallet
MAESTROCards
MASTERCARDCards
VISACards

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.

FeatureSupportedNotes
3DS 2.0 ExternalYes
3DS 2.0 PaymentsOS-handledNo
3DS 2.0 Provider-handledNo
3DS 2.0 Self-handledYesSupported flow type: Self-handled Flow. For more information, see 3DS 2 Self-handled Flow.
InstallmentsNo
Level 2 and 3 DataNo
Multi-seller PaymentsNo
Network TokensNo
Payment FacilitatorNo
PayU RiskNo
Pre-authorizationYes
Retrieve Supported Payment MethodsNo
Retrieve Supported PlansNo
Statement Soft DescriptorNo
Stored Credentials FlagYes
Transaction Processing without CVVYes

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.

Supported requests for card transactions.
Request Partial/Multiple Mode
Authorize Partial and multiple are not supported Synchronous
Capture Both partial and multiple are supported Synchronous
Charge Not Applicable Synchronous
Credit Partial and multiple are not supported Synchronous
Refund Both partial and multiple are supported Synchronous
Void Both partial and multiple are supported Synchronous
Supported requests for eWallet transactions.
Request Partial/Multiple Mode
Authorize Partial and multiple are not supported Asynchronous
Capture Partial and multiple are not supported Asynchronous
Charge Not Applicable Asynchronous
Refund Multiple is supported Asynchronous
Void Not Applicable Synchronous

Setup Procedures

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

ConfigurationRequired/Optional
In the PaymentsOS Control Center, configure the following credentials:
  • merchant_id: The merchant id as defined in your Finaro account.
  • signature_key: The SHA256 signature key you received from Finaro
Required
In your Finaro account, configure SHA256 hashing (used for authentication purposes).Required
In your Finaro account, enable the currencies you require in your transactions. Contact Finaro support for assistanceRequired
In your Finaro account, enable the transaction request types you would like to use. Note that Operation code 101 (Past Transaction Retrieval) is required. The other request types are optional.
  • Operation code 101 (Past Transaction Retrieval). This is required for PaymentOS to remain in sync with the transaction status.
  • Operation code 92. This is required for 3DS internal transaction flows.
  • Charge. This is operation code 1 in your Finaro account.
  • Authorization. This is operation code 2 in your Finaro account.
  • Capture. This is operation code 3 in your Finaro account.
  • Authorization Void. This is operation code 4 in your Finaro account.
  • Refund. This is operation code 5 in your Finaro account.
  • Credit. This is operation code 6 in your Finaro account.
  • Charge Void. This is operation code 7 in your Finaro account.
  • Capture Void. This is operation code 9 in your Finaro account.
Required
In your Finaro account, disable the CVV check if desired. Contact Finaro support for assistance.Optional
In your Finaro account, enable a Dynamic Billing Descriptor. This requires approval from Finaro.Optional
If you would like to start using 3DS with Finaro, do the following:
  • For using external or internal 3DS, contact Finaro for registering with the card schemes.
  • To use the internal (Source's) 3D Secure service, you must be registered to the service and have it activated on your account. Contact your Finaro account manager for more information. Note: Source’s 3D Secure service supports both versions of the 3D Secure protocol: 3D Secure 1.0 and 3D Secure 2.0.
  • If you want to use the SMART 3DS fraud service, enable SMART 3DS in your Finaro account.
  • If you want to use 3DS Advisor, enable 3DS Advisor in your Finaro account.
Beware:
  • PaymentsOS does not support a flow with Finaro in which a 3D Secure authentication process is executed without actually processing the transaction.
  • If you did not enable the internal (Source's) 3D Secure service in your Finaro account, the transaction will fail if you pass 3DS data in your transaction requests when sent as part of an internal 3DS flow.
  • You cannot use an external 3DS service in combination with the internal (Source's) 3D Secure service. This means that if the transaction contains both the provider_specific_data.credorax.additional_details.three_d_secure_initiate field and the three_d_secure_attributes.external fields, the transaction will be declined.
Optional

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.

Last modified July 17, 2023