All pages
Powered by GitBook
1 of 12

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Product description

Field name
Type
Description

Product code*

Text

Enter a unique code for the card product.

Note: Spaces are not allowed in the product code, you can use an underscore instead.

Product name*

Text

Enter a unique product name.

Country of issuing*

List

Select the country of issuing the card. This is a predefined list.

Organization unit*

List

Select an organisation unit from the drop-down menu. The organisation unit is used to manage users and their roles.

Create card products

Prerequisites

Prior creating a new card product, complete the required setup:

After completing the required steps, you can proceed with the card product creation.

Create card product

To create a new card product, go to:

  1. Cards > Products > Card products.

  2. On the Card products page, click the Add new product button.

By default the Card products page shows the list of all existing card products.

  1. Fill in the following card product parameters:

Click on the card parameters groups to view detailed information.

  1. Click Submit to finalise the card product creation.

.

.

, if required.

,

,

,

,

,

,

,

,

.

Add a BIN
Create a card price list
Add fee cap
Product description
Card account settings
Card main settings
PAN settings
Product price lists
Product designs
MCC settings
Authorisation types
Other card parameters

Card account settings

Field name
Type
Description

Account owner type*

List

Select the type of account owner.

The possible values are:

  • All

  • Private

  • Legal

Account source*

List

Select the account source.

The possible values are:

  • Account-api account

  • Card-api account

  • External account

PAN settings

Field name
Type
Description

PAN length*

Number

Enter the PAN length.

The length of a payment card number is a number between 13 and 19 (including both).

Default value: 16

BIN number (6 or 8 digits)*

List

Select from predefined BINs, specific to the Card Scheme.

BIN additional (2 digits)

Number

Enter the additional BIN. This allows to define the account range within the BIN. This refers to the 2 digits that the issuer can use to identify. For example, different card products or different currencies.

Reserved range from*

Number

Enter the reserved range inside the full PAN free range.

Reserved range to*

Number

For information on adding BIN numbers, see .

Add a BIN

Product price lists

Select the allowed price lists and a default price list for the card product. Only one price list can be the default price list. For details about how to create price lists, see .

Create price list

Card main settings

Field name
Type
Description

Card Scheme*

List

Select one of the following card schemes:

  • MasterCard

  • Visa

Card program*

List

Select one of the following card programs:

  • Debit

  • Credit

Default value: Debit

Card type*

List

Select one of the following card types:

  • Physical

  • Virtual

Default value: Physical

Note: A physical card can have all the features of a virtual card.

Reporting product code

List

Card currency*

List

Select the currency for the card product.

Default value: EUR

Settlement currency*

List

Select the currency that is used for bank transactions.

This is an informational field only. This means that although you can select the settlement currency, this field is not used in any process. The value is defined between the bank and the scheme.

Default value: EUR

Card expiry (in months)*

Number

Enter the number of months for which the card is valid.

Default value: 36

Default credit type*

(For credit cards only)

List

Select the default credit product.

This field is displayed only when you have selected Credit in the Card program field.

Personalisation profile ID*

Text

Enter the personalisation profile ID. It is the agreed value with the personalisation centre by the issuer.

Note: This field is displayed when the Card type is Physical.

Card default delivery method*

List

Select one of the following methods of card delivery:

  • Delivery by courier

  • Delivery by post

Note: This field is displayed when the Card type is Physical.

PIN default delivery method*

List

Select one of the following PIN delivery methods:

  • From service (The PIN is sent via SMS, email, or internet banking)

  • Delivery by post

Default value: From service

Card vendor ID*

Text

Enter the card vendor ID. The value must be 2 digits.

Note: This field is displayed when the Card type is Physical.

PAN service code*

Text

Enter the PAN service code. The service code is a value defined by card schemes and defines various services, differentiates card usage in international or domestic interchange, designates PIN requirements, and identifies card restrictions.

Note: This field is displayed when the Card type is Physical.

The following screenshots show the settings for debit cards:

Physical debit card
Virtual debit card

The following screenshots show the settings for credit cards:

Physical credit card
Virtual credit card

About reporting product code

The reporting product code refers to the category of product or service. Reporting product codes are used for most finance and reporting purposes.

For the card module, the reporting product code is included in all transaction and contract event messages. The finance API consumes these event messages and uses them for reporting. In the Tuum financial entries, the reporting product codes can be used with the GL accounts that are related to the customer account or contract and represent the receivables or payables, and the related revenue or expenses.

The usage of reporting product codes is optional for organisations. If your organisation has not opted to use the reporting product codes, they are not part of your Tuum system configuration.

You need to select reporting product codes for the following entities:

  • For each debit card product that you create.

  • For credit types.

  • For credit card instalment plan types.

You can use the same reporting product code for different card products.

You cannot use the reporting product codes for the following:

  • Transit type of GL accounts. For example, payment transit accounts or transit accounts between the Tuum business modules.

  • Nostro accounts and the related fees or interest.

To manage lookup codes, select Administration > Settings > Lookups. From the left-hand menu, select the COMMON.REPORTING_PRODUCT_CODE lookup. The codes are defined with the entity name COMMON.REPORTING_PRODUCT_CODE and the lookup type code VALUE. The list is used by all the modules and you cannot create separate codes for different entities.

The following screenshot shows the list of lookup codes:

Select a reporting product code from the drop-down menu. See for details.

Note: The selection list includes predefined active credit products. You can if you need to.

To create more codes, click the plus icon . You can edit the codes by clicking the edit icon . After this, the codes will be available to use when you are creating debit card products, credit types, and instalment plan types.

You can also create lookup codes using the API endpoints. To know more about this, see the of the API Cookbooks.

lookup section
configure new credit products
About reporting product code

Authorisation types

The authorisation types allowed for a card product are handled by usage groups assigned to the card product. The defined groups can be shared across multiple card products.

  • Usage group - A group that controls where a card can be used. For example, in ATMs, for e-commerce, and for contactless purchases.

  • Upper usage group - A group with the maximum allowed authorisation types.

  • Default usage group - The default group for the card product.

  • Allowed authorisation types (service codes) - The allowed authorisation types on the cards.

To create a new usage group, click Create usage group.

  • On the New usage group window that opens, enter the name and the organisation unit.

  • The usage group that you are creating must be defined as an upper usage group or must be linked to an upper usage group.

  • Select the authorisation types from the list and click Submit.

You can also create and view existing groups from Cards > Usage group.

MCC settings

The MCC (Merchant Category Codes) are four-digit numbers used to categorise the transactions and to classify merchants and business by the type of good or services provided.

The Tuum system allows setting up two types of MCC groups:

  • Whitelist - only the authorisations with the MCC groups that are defined in whitelist are allowed, other authorisations will be declined.

  • Blacklist - all authorisation requests with the MCC groups that are defined in blacklist will be declined.

When setting up a card product you can define one or many Allowed mcc groups and set one default mcc group.

Once the allowed and default mcc groups are selected, click the Create mcc group button and fill in the following parameters, click Submit:

  • Mcc group name - Enter a group name. It can only consist of the upper-case letters, numbers and underscores. It must start with a letter and cannot end with an underscore.

  • Control Type - Select if the group is whitelisted or blacklisted.

  • Mcc codes - Select the relevant mcc codes. You can select multiple values.

  • Organisation unit - Select the organisation unit from the list.

Product designs

A design ID is the value agreed with the card manufacturer and this information is provided with the request sent to the processor when ordering a physical plastic card. You must define at least one product design to be able to create a card product. The maximum length for a design ID is defined within the System property under Settings.

This section is displayed only when the Card type is Physical.

Select the allowed product designs and a default product design. Only one design can be the default product design.

To create a new design, click Create design. Enter the design code and provide a description.

Card level default limits

The card usage limits allowed for a card product are handled by limit groups assigned to the card product. The defined groups can be shared across multiple card products.

  • Limit group - A group that controls the allowed limits for authorisation types with defined upper and default limits.

  • Upper limit group - A group with the maximum allowed limits.

  • Default limit group - The default group for the card product.

To create a new group, click Create limit group.

  • On the New limit group window that opens, enter the group name and the organisation unit.

  • If the limit group you are creating is not an upper limit group, then you must select an upper limit group.

  • If you are creating an upper limit group, it is optional to select an upper limit group.

  • Click Add limit to select the limit type and the currency. Enter the limits for the limit type.

  • You can add more limits by clicking Add limit and when you are done, click Submit.

You can also create and view existing groups from Cards > Limit group.

MCC settings are optional. If not required, you can skip this section and continue with the .

authorisation types

Completing card product creation

Click Submit to create the card product.

The card product created is inactive. Please refer to the to learn more.

Card Product Statuses

Additional settings

Field name
Description

Is card replaceable?

Note: This field is displayed when the Card type is Physical.

Is card renewable?

The checkbox is selected by default.

Card application needs acceptance?

Select whether the card application requires acceptance for card creation.

Card is useable before delivery?

Select whether the card can be used for transactions before the delivery of the physical plastic card.

Note: This field is displayed when the Card type is Physical.

Order plastic automatically?

Select whether the physical card is ordered automatically with the creation of the card.

Note: This field is displayed when the Card type is Physical.

Is AVS required?

Select whether Address Verification Service (AVS) is required.

The following table shows the additional settings for physical and virtual card types:

Card type = Physical
Card type = Virtual