The authorization workflow process (authentication checks list, financial checks list) is set-up during the design phase.
Several API are provided so that the issuer can retrieve the configuration and potentially override the controls for a given cardholder.
Standard Authorization Restrictions can be changed by creating Authorization Restriction Overrides.
In the below diagram, several use cases covered by this domain are illustrated.
Account Reference
Card Controls for a card are linked to the "Account" set up for the card ("Account Model").
The “Account” resource is identified (hence accessed) by an account reference, that was:
w generated by Worldline (said “internal” to WL system) and transmitted to the Issuer;
(NB this mandatory “internal” reference acts as a key for accessing the resource)
w -or- provided by the Issuer (said “external” to WL system) at the resource creation.
(NB this optional “external” reference may ease integration or use at Issuer side.)
Accordingly, account operations may be called via two different paths:
(with the appropriate parameter as it is required in each specific path)
w "/issuers/{issuerId}/accounts/{accountReference}/" -or-
w "/issuers/{issuerId}/accounts/external-accounts/{issuerAccountExternalReference}/".
Control Types
Card Controls are composed of Authorization Restrictions and Velocity Limits .
They are set-up according to the applicable “Restriction Model” linked to the “Account Model”,
configured according to the specific product initial setup with the values applicable by default,
(that is, the model selected in the template of the product, where default values are defined)
(hence, depending on the customer-specific configurations, subject to bilateral agreements)
and can next be changed for a given account via overrides (creation and update or deletion).
They apply during the authorization process (besides the authentication or financial checks).
These configuration data are identified via references, kind of descriptive strings serving as identifiers.
The references for the authorization restrictions and velocity limits are agreed bilaterally with the issuer.
NB they are the "{authorizationRestrictionReference}" and "{velocityLimitReference}" in the calls.
The references for their respective overrides, if any, are generated by Worldline at the override creation.
NB i.e., the "{authorizationRestrictionOverrideReference}" and "{velocityLimitOverrideReference}".
Remark: refer to the Resource References of the "Data Model" in the Core Concepts.
Related API operations can be used, per account:
w to retrieve the applicable configuration settings;
w to override given control[s] (restriction[s], limit[s]).