Title bar text

Issuer

Issuer Product

Contract

Contract refers to the consumer and corporate contracts created in OPC (Offers, Products & Contracts) service using the provided product as template for the structure and default values. Products are built from Account and Card Templates, Profiles and Add-on services.

Contract Saving Measures

Saving measures are activated and deactivated on a contract for risk management purposes. They are used to close online services through authorization methods, lower Online Limits, update authorization methods with immediate payment mode to set the Force Account Check, switch account card payment from deferred to immediate payment mode, forbid cards delivery, block EMV Card Applications, put under control EMV Card Applications, deactivate Contactless Cards.

Card Contract

A card contract can be created for a card holder or as an anonymous contract. When creating a card from a card contract, a number of parameters are calculated based on the settings in the card profile, the selected models and the card contract.

Card

A card let cardholders access funds in checking or savings accounts or make purchases against a line of credit. Card types are being defined by a card schemes and a brand (e. g. Visa Classic Card, Visa Gold Card, MasterCard Standard, MasterCard Gold).

Card Order

An order refers to Card Order and PIN Mailer data extractions that are sent to Card Producer and PIN Mailer Editors respectively.

Customer

A customer is a person (individual) or a company who has subscribed to services offered by the issuer.

Customer Address

A customer Address is the generic term for postal address, email address or phone number. 

Addresses can be of two types; Personal Address or Company Address.

Addresses could get multiple usages describe which address is used and in which service. These usages are defined in the corresponding service; Account Service (Statement Sending, Invoice Sending) and Card Service (Virtual Card Sending, Card Delivery, PIN mailer Delivery, Activation Mode Delivery).

Account

Accounts are independent from any payment mean. They are used to process operations, manage a balance in a dedicated currency,  control the credit risk, perform transaction charging, calculate interests (credit or debit), generate an invoice (statement), process payments. Three types of accounts working modes are being supported; Pay Before, Pay Now, Pay Later.

Accounts are linked to form a hierarchy in order to set up multi-purpose products (mixture of debit and credit accounts), represent organizations (families or corporate structures), set up multi-currency accounts. Credit risk verifications can be expanded across the hierarchy. Consolidated invoicing and payment management is done on top level account for accounts lower in the hierarchy.

Account Authorization Restrictions 

The purpose of a restriction is to allow or refuse a transaction based on given rules. These rules are
implemented with an initial customer specific setup in Worldline Pay Front Office. Like this, a set of customer
specific standard restrictions can be implemented. The standard restrictions are permanently, but can be
changed, i.e. overwritten by using the Card Control API.
The approval and the refusal of transactions are managed by turning on or off - or by blocking or unblocking -
the concerned standard restriction.

The standard restrictions for Card Control are to block or unblock of :

• cards temporarily or permanently
• channels like
  • ATM / cash
  • card present (POS)
  • card not present (eCommerce, telephone)
  • card not present recurring
  • contactless online (NFC online)
  • magstripe
• a single country, a list of single countries
• regions (Geo Blocking)
• merchant category codes (MCC Blocking)

It is also possible setup a mix of restrictions in WLP-FO, e.g. block or unblock ATMs in South Africa.

Each of these standard restrictions is per default set as blocked or unblocked, depending on the customer’s
need.

Each of the listed standard restrictions can be blocked or unblocked by calling the appropriate web service of
the Worldline Premium Gateway API. If the user e.g. blocks a card by using the appropriate web service, the
card is blocked immediately and without an end date.

Account Authorization Velocity Limits

The purpose of a velocity limit is to limit a transaction in terms of amount and frequency, e.g. it might be
allowed to withdraw 2,500€ per day on POS terminals in Europe.
The velocity limits are implemented with an initial customer specific setup in Worldline Pay Front Office. Like
this, a set of customer specific standard velocity limits can be implemented. The standard velocity limits are
permanently, but can be changed, i.e. overwritten by using the Card Control API.
The standard velocity limits for Card Control are

• Cash (ATM, branch, POS)
• eCommerce
• POS
• NFC

Depending on the customer’s need, each of the standard velocity limits is set per default with

• a minimum amount and a flag, if this amount should be checked
• a maximum amount and a flag, if this amount should be checked
• a maximum counter and a flag, if this amount should be checked

A default velocity limit can further be combined with a country or a region, e.g.

• ATM daily limit in the Netherlands
• ATM daily limit in the Europeen Economic Area (w/o the Netherlands)
• ATM daily limit worldwide (w/o the EEA)

  ---

Account Authorizations

Authorizations are approvals from a card issuer that the cardholder has sufficient funds to cover the cost of the transaction.

Account Credit Limit

Credit limits are applicable to Pay Later account types. A credit limit is the maximum amount of money an account owner can borrow. An account will typically have a single overall credit limit that restricts the total amount of unsettled activity permitted against the account.

Account Credit Installement Contract

Account Operations

Operations are posted on accounts, It could be clearing transactions, internal fees and interests, refund and redebits from Dispute management.

Account Statements

Dispute

Dispute cycle management provides the full life cycle management and organization of disputed transactions. A transaction can be disputed for a number of different reasons, such as when a cardholder detects that the transaction has been executed twice, when he does not recognize the transaction on his statement, or when services for the transaction were not delivered.