Important Integration Settings

Each integration method's features may require different settings to work properly. The main settings you should be aware of before starting your integration are covered below.

By Integration Method

Hosted Payment Page (HPP)

Enabling Method and Features for Terminal

Terminals need the “Allow Internet” permission to be enabled to use them with the HPP.

This setting must be configured by our Support Teams - verify before integrating.

Styling Your Hosted Pages

The Hosted Payment Pages can be styled. For details on styling the Hosted Payment Pages, see the section Pay Pages.

Styling is performed by the Merchant.

XML Integration

Enabling Method and Features for Terminal

Terminals do not need any special configuration to use the XML Integration. However, depending on the transactions you intend to process, settings may need to be adjusted. Confirm with our support team if the Terminal you are trying to use allows the use of XML Integration.

By Feature

Several features require configuration to work properly. Most are configured at Terminal Level, so ensure they are accessible to the Terminal you are using.

All of the settings below must be configured by our Support Teams - verify before integrating.

Secure Card Settings

Merchant Portfolio Settings

At this level, when a Merchant Portfolio is configured, three different settings can be used to define how the the Secure Card Registration and the Payment using a Secure Card should occur for its Merchants:

Enable SecureCard Auto Registration: when enabled, automatically creates Secure Cards (tokens) when Payment transactions occur.
Enable SecureCard Uniqueness: when enabled, a Secure Card is unique within the Merchant Portfolio scope (all the Secure Cards of all the Merchants' Terminals). When disabled, a Secure Card is unique within the Terminal's scope.
Enable SecureCard Auto Sharing: when enabled, a Secure Card created within the Merchant Portfolio (all the Secure Cards of all the Merchants' Terminals) is made available to be used for payment by all the Merchants' Terminals. When disabled, leaves the configuration to Merchant Level.

Merchant Settings

Any merchant can choose between sharing its Secure Cards among all of its Terminals, or not, using the following property:

Share all Secure Cards: When enabled, allows any Terminal from this specific Merchant to use Secure Cards of its other Terminals to process transactions. When disabled, the sharing is not allowed and each Terminal can only use its own Secure Cards.

However, if the Merchant is associated to a Merchant Portfolio with Enable SecureCard Auto Sharing enabled, its Share all Secure Cards is automatically enabled.

Terminal Settings

The most basic configuration required to use Secure Card is enabling it at the Terminal Level.

Subscription Settings

The Subscription feature requires Secure Card to be enabled (and actual Secure Cards (tokens) registered). Once Secure Card is enabled, the Subscription feature itself needs to be enabled and the following items need to be configured:

FIELD	DESCRIPTION
Subscription max wait for payment, days	Defines the amount of days a subscription's payment can be delayed before the system suspends the given subscription.
Subscriptions max missed periods	Defines the amount of times a subscription can miss payments before being suspended by the system.
Subscriptions payment notification, days	Defines the amount of days the system waits until sending the notification warning for a subscription which couldn't be paid.
Subscription missed periods notification	Defines the amount of times a subscription can miss payments before the system starts sending warning notifications about it.
Subscription repeat notification, days	Defines the amount of days the system waits until sending the next notification warning about a subscription which is still not paid.
Subscription auth max attempts	Defines the amount of authorization attempts the system will try before suspending an automatic subscription.