Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
developer:important_integration_settings [2018/12/03 10:26] 127.0.0.1 external edit |
developer:important_integration_settings [2022/03/18 12:19] (current) lezlieh update with secure token |
||
|---|---|---|---|
| Line 54: | Line 54: | ||
| </WRAP> | </WRAP> | ||
| - | ==== Secure Card ==== | + | ==== Secure Token==== |
| **Merchant Portfolio 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: | + | At this level, when a Merchant Portfolio is configured, three different settings can be used to define how the the Secure Token Registration and the Payment using a Secure Token should occur for its Merchants: |
| - | * **Enable SC Auto Registration**: when enabled, automatically attempts to create Secure Cards when Payment transactions occur. | + | * **Enable SC Auto Registration**: when enabled, automatically attempts to create Secure Tokens when Payment transactions occur. |
| - | * **Enable SC Uniqueness**: when enabled, a Secure Card is unique within the Merchant Portfolio scope (all the Secure Cards of all the Merchants' Terminals), but when disabled, a Secure Card is unique within the Terminal's scope. | + | * **Enable SC Uniqueness**: when enabled, a Secure Token is unique within the Merchant Portfolio scope (all the Secure Tokens of all the Merchants' Terminals), but when disabled, a Secure Token is unique within the Terminal's scope. |
| - | * **Enable SC 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. Disabled, leaves the configuration to Merchant Level. | + | * **Enable SC Auto Sharing**: when enabled, a Secure Token created within the Merchant Portfolio (all the Secure Tokens of all the Merchants' Terminals) is made available to be used for payment by all the Merchants' Terminals. Disabled, leaves the configuration to Merchant Level. |
| | | ||
| **Merchant Settings** | **Merchant Settings** | ||
| - | Any merchant can choose between sharing its Secure Cards among all of its Terminals, or not, using the following property: | + | Any merchant can choose between sharing its Secure Tokens 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. | + | * **Share all Secure Tokens:** When enabled, allows any Terminal from this specific Merchant to use Secure Tokens of its other Terminals to process transactions. When disabled, the sharing is not allowed and each Terminal can only use its own Secure Tokens. |
| - | However, if the Merchant is associated to a Merchant Portfolio with **Enable SC Auto Sharing** enabled, its **Share all Secure Cards** is automatically enabled. | + | However, if the Merchant is associated to a Merchant Portfolio with **Enable SC Auto Sharing** enabled, its **Share all Secure Tokens** is automatically enabled. |
| **Terminal Settings** | **Terminal Settings** | ||
| - | The most basic configuration required to use Secure Card features is the enabling of this feature at Terminal Level. | + | The most basic configuration required to use Secure Token features is the enabling of this feature at Terminal Level. |
| ==== Subscription ==== | ==== Subscription ==== | ||
| - | First of all, the Subscription feature requires the enabling of the **Secure Card** features to be used (and actual secure cards registered). | + | First of all, the Subscription feature requires the enabling of the **Secure Token** features to be used (and actual secure tokens registered). |
| Secondly, the Subscription feature itself needs to be enabled and the following items need to be informed. | Secondly, the Subscription feature itself needs to be enabled and the following items need to be informed. | ||