Card Management System (CMS)

We understand that every organization and payment system is unique, and we acknowledge the necessity to customize the solutions to fit your specific needs. Our Card Management System (CMS) provides a range of card product options with highly customizable attributes and management features. With CMS, you can control the entire card product life cycle, encompassing cards, accounts, cardholders and card product definitions.

The foundational elements in CMS are Card Product Definitions (CPDs) and Cards, serving as sources for settings, limits, and restrictions specific to a product line and personalized preferences for one’s card itself.

Card Product Definition (CPD)

Card Product Definitions (CPDs) function as product profile i.e. physical debit card or virtual credit card. CPDs are not restricted only to card types but can use all settings and restrictions available in CMS. If a card is generated based on a predefined CPD, it is created according to all the configurations and limitations associated with that CPD.

CPD sets:

• Card association
• Card technology (i.e. Virtual, Contactless, Magnetic stripe etc.)
• Card type (i.e. Credit, Debit)
• Card limit ranges and restrictions
• Card product PAN (Primary account number = card number) range
• Segment (i.e. Retail, Corporate etc.)
• Immediate digital activation
• Card default expiration
• Card graphic design
• Card delivery type
• Option to view/change PIN
• Option to have embossed name
• Autorenewal

Additionally, CPD allows to set its own successor, which comes into play in the event of CPD deactivation and is subsequently utilized as the primary product profile for card creation.

“For instance, our primary product line, a physical debit card, is undergoing a graphic design update. The current settings are stored within the current active version of CPD, referred to as CPD_v1. With the introduction of the new graphic design, a new CPD_v2 is created and designated as the successor to CPD_v1. When it is time to kick off the new card design, CPD_v2 is activated, and new cards are generated with the updated design.”

Example above can be used for every aspect of CPD settings, which allows smoothly switch between new versions of product.

The complexity of CPD settings is clearly demonstrated by the ability to establish card limits ranges and card restrictions based on product line preferences. Limits range and restrictions can be configurated and adjusted in advance, prior to their utilization in CPD, to encompass all Card Product specifications designed by our client.

The existing limit ranges that can be include in CPD:

• POS transaction limit range
• E-commerce transaction limit range
• ATM withdrawal limit range

Additional complexity is introduced through card restrictions, which enables the setting of restrictions based on transaction type, location, transaction technology used, DCC transactions, and more.

The existing restrictions that can be include in CPD:

• Restriction of cash transactions
  

• Restriction of contactless transactions

• Restriction of online transactions

• Restriction of magstripe transactions

• Restriction of DCC transactions

• Restriction of Chip\&PIN transactions

• Restriction of mobile wallets transactions

• Restriction of MCC transactions

• Restriction based on location given by country codes

• Restriction based on transaction types permissions

An example of a working CPD, including all limit ranges and restrictions, can be found here.

Card

A card is a payment instrument available in physical and virtual (or tokenized) forms. Each card is assigned a unique card number, along with a specified expiration date and CVV/CVC. In CMS, the card is linked to an account and possesses attributes determined by CPD, as well as preferences configured during card creation, if allowed by CPD.

Since CPD provides information about transaction limit ranges, it is necessary to specify the actual limit within the range for the specified card. Similarly, the same logic applies to card restrictions; if CPD allows customer modifications, the desired values for such restrictions must be provided in the request and will be subsequently used; otherwise, the restrictions are set by CPD and will be applied according to CPD.

Once a card is created, it enters the lifecycle as outlined in the basic description below.

#	Status change	Description
	New -> Inactive	New card is requested at Card processor.
	Inactive -> Digitally active	New card number is provided by Card processor and physical card is digitally activated according to Card processor.
	Digitally active -> Active	Manual activation of physical card is initiated and completed.
	Active/Digitally active/Blocked -> Revoked	Card is revoked and its lifecycle ended.
	Active/Digitally active -> Blocked	Card is temporary blocked due to fraud, owner decision etc.
	New/Inactive -> Cancelled	Requested unused new card is cancelled.
	New -> Active	New virtual card has been confirmed by Card processor and new card number have been assigned and activated.
	New -> Digitally active	New card number is provided and physical card is immediately digitally activated.
	Inactive -> Active	New card number of physical card (which cannot be tokenized) is provided and manual card activation is completed.

Throughout its entire life cycle, the Card is associated with a single account and a single cardholder. While the cardholder may be the same person as the account owner, it is not a requirement.

In the event of the card expiration, CMS automatically renews the card with the same PAN but different CVV/CVC and expiry date. If the card is lost or stolen, it is replaced, and the new card is issued with a new PAN, CVV/CVC, and expiry date.

In the CMS, the Card stores the following attributes:

• CPD code
• Card ID
• Card status
• Cardholder details
• Account details
• Card truncated PAN
• Card association
• Card type (i.e. Credit, Debit)
• Card limit ranges and restrictions
• Segment (i.e. Retail, Corporate etc.)
• Immediate digital activation
• Card validity from and to
• Card graphic design
• Card delivery address and type
• Embossed information
• Autorenewal
• Block information

An example of a working card, including all limit ranges and restrictions, can be found here.

Account

An account is linked to at least one card, providing a connection to the balance that can be used for transactions. When a transaction is authorized, adhering to all limits and restrictions set by CPD and the card, a hold is created on the account, deducting the available balance until the transaction is settled.

The account is linked to a specified owner in a specified currency. If a transaction is made in a different currency, an exchange rate conversion is used to ensure that limits and balance checks are processed correctly.

Similar to blocking a card, an account can also be blocked to ensure that no funds are withdrawn. During this procedure, all connected cards are also blocked.

Main account attributes are listed below:

• Card ID
• Account status
• Account owner ID
• Account owner name
• Account ID
• Account currency

Limits and restrictions

Limits and restrictions enable the customization of card products, allowing personalized settings for end customers. The CMS establishes limit ranges for CPDs, along with specific limit values within CPD limit ranges for new cards. Following the same logic, CMS predefines limits and restrictions, and these limits and restrictions are set for the card during creation. For example, if an ATM withdrawal restriction is included and available for modification in CPD, it is possible to set or not set this restriction for a new card. Non-modifiable restrictions are set for the card by default.

The CMS enables the configuration of specific limits and restrictions, i.e. allowing any combination of parameters from various pre-existing limits or restrictions. When all required parameters are incorporated into the Authorization request, the CMS can then implement any limit or restriction in accordance with the client's preferences.

To set a limit for a card, the ID of the limit must be provided along with all the necessary values. All limits included in CPD, which allows modifications must be included in a request for a new card. If a limit has a range of values set by CPD, the CMS will allow only setting limit value in this range. Limits can be configured for daily, weekly, and monthly periods, encompassing both amount and count settings.

To set a restriction for a card, the ID of the restriction must be provided along with all the necessary values. All restrictions included in CPD, which allows modifications must be included in a request for a new card.

Restrictions can be established using the logic of a blacklist, whitelist, or a specific flag from transaction data to either restrict or allow specific transaction configurations.

Editing limits and restrictions settings is permissible after card creation using PUT/cards/{id}/limits and PUT /cards/{id}/restrictions, subject to the preferences of the owner or cardholder, provided that the settings for the restriction or limit allow such modifications.

POS transaction limit

To establish a specific limit range for all POS transaction types, the configuration can be defined by specifying the relevant POS transaction types. This configuration is then transmitted to the Authorization core, where transaction amounts for these specified transaction types are cumulated over the set period. In the event of exceeding the established limit, any subsequent transactions are declined.

Name	POS Transaction Types	Direction
CSD	Cash advance	Debit
CSR	Cash advance Reversal	Credit
RTL	POS Purchase	Debit
RTR	POS Purchase Reversal	Credit
CBN	POS Cash-back	Debit
CBR	POS Cash-back Reversal	Credit
RET	Merchandise return	Credit
RER	Merchandise return Reversal	Debit
CNP	Card-Not-Present (except e-commerce)	Debit
CNR	Card-Not-Present Reversal (except e-commerce)	Credit
CRP	Card-Not-Present return (except e-commerce)	Credit
CRR	Card-Not-Present returm Reversal (except e-commerce)	Debit
GAM	Gambling	Debit
GAR	Gambling Reversal	Credit
PRE	POS Pre-authorization purchase	Debit
PRR	POS Pre-authorization purchase Reversal	Credit
QUA	Quasi-Cash	Debit
QAR	Quasi-Cash Reversal	Credit

E-commerce transaction limit

To establish a specific limit range for all E-commerce transaction types, the configuration can be defined by specifying the relevant E-commerce transaction types. This configuration is then transmitted to the Authorization core, where transaction amounts for these specified transaction types are cumulated over the set period. In the event of exceeding the established limit, any subsequent transactions are declined.

Name	E-commerce Transaction Types	Direction
ECP	E-commerce purchase	Debit
ECR	E-commerce purchase Reversal	Credit
EME	E-commerce Merchandise return	Credit
EMR	E-commerce Merchandise return Reversal	Debit
EGM	E-commerce Gambling	Debit
EGR	E-commerce Gambling Reversal	Credit
EPA	E-commerce Pre-authorization purchase	Debit
EPR	E-commerce Pre-authorization purchase Reversal	Credit

ATM withdrawals limit

To establish a specific limit range for all ATM withdrawals transaction types, the configuration can be defined by specifying the relevant ATM withdrawals transaction types. This configuration is then transmitted to the Authorization core, where transaction amounts for these specified transaction types are cumulated over the set period. In the event of exceeding the established limit, any subsequent transactions are declined.

Name	ATM withdrawals Transaction Types	Direction
ATM	ATM withdrawal	Debit
ATR	ATM withdrawal Reversal	Credit

Restriction of cash transactions

To implement a restriction preventing all cash transactions, blacklist logic is used to disallow specific transaction types from receiving approval. The most efficient approach for restricting a limited number of items is through the application of blacklist logic. This method necessitates the explicit specification of each restricted item in the blacklist, ensuring control over the items subjected to the restriction.

Name	Cash Transaction Types	Direction
ATM	ATM withdrawal	Debit
ATR	ATM withdrawal Reversal	Credit
CSD	Cash advance	Debit
CSR	Cash advance Reversal	Credit

Restriction of contactless transactions

To implement a restriction preventing all Contactless transactions, Transaction flag logic is used to disallow one specific transaction flag from receiving approval. This is the most efficient approach for restricting a single item. Specific value is provided by Card processor and translated to Authorization core data structure i.e. Field 22 POS Data Code – position 7 (Card data input mode) for values “A” and “M” are indicators for contactless transactions. All authorization requests with this value are declined.

Restriction of online transactions

To implement a restriction preventing all Online transactions, Transaction flag logic is used to disallow specific transaction flag from receiving approval. This is the most efficient approach for restricting a single item. Specific value is provided by Card processor and translated to Authorization core data structure i.e. Field 22 POS Data Code – position 5 (Cardholder present) for value “5” and position 7 (Card data input mode) for values “N”,”R”, “U”, “V”, “S” and “T” are indicators for online transactions.

Restriction of magstripe transactions

To implement a restriction preventing all Magstripe transactions, Transaction flag logic is used to disallow specific transaction flag from receiving approval. This is the most efficient approach for restricting a single item. Specific value is provided by Card processor and translated to Authorization core data structure i.e. Field 22 POS Data Code – position 7 (Card data input mode) for values “2”, “8” and “9” are indicators of magnetic stripe transactions.

Restriction of DCC transactions

To implement a restriction preventing all DCC transactions, Transaction flag logic is used to disallow specific transaction flag from receiving approval. This is the most efficient approach for restricting a single item. Specific value is provided by Card processor.

Restriction of Chip&PIN transactions

To implement a restriction allowing only Chip&PIN transactions, Transaction flag logic is used to disallow specific transaction flag from receiving approval. This is the most efficient approach for restricting a single item. Specific value is provided by Card processor and translated to Authorization core data structure i.e. Field 22 POS Data Code – position 5 (Cardholder present) for value “5” are indicators of Chip&PIN transactions.

Restriction of mobile wallets transactions

To implement a restriction preventing all mobile wallets transactions, Transaction flag logic is used to disallow specific transaction flag from receiving approval. This is the most efficient approach for restricting a single item. Specific value is provided by Card processor.

Restriction of MCC transactions

To implement a restriction preventing all transactions with specified MCC, blacklist logic is used to disallow transactions with specific MCC from receiving approval. The most efficient approach for restricting a limited number of items is through the application of blacklist logic. This method necessitates the explicit specification of each restricted item in the blacklist, ensuring control over the items subjected to the restriction.

Example of possible list of restricted MCC:

• 7995 – Betting (including Lottery Tickets, Casino Gaming Chips, Off - track Betting and Wagers)
• 7800 – Government-owned lotteries
• 7801 – Government licensed casinos (Online gambling)
• 7802 – Government licensed horse/dog racing
• 5967 – Direct marketing, inbound teleservices, audiotext & videotext

Restriction based on location given by country codes

To implement a restriction allowing only transactions from specified countries, whitelist logic is used to allow transaction from specified countries to be approved. The most efficient approach for allowing a limited number of items in large pools of other possibilities is through the application of whitelist logic. This method necessitates the explicit specification of each allowed item in the whitelist, which ensures that transactions involving these specified items are permitted and can be approved.

In case only EU states are allowed, then whitelist will look like this:

• AUT, BEL, BGR, HRV, CYP, CZE, DNK, EST, FIN, FRA, DEU, GRC, HUN, IRL, ITA, LVA, LTU, LUX, MLT, NLD, POL, PRT, ROU, SVK, SVN, ESP, SWE

Restriction based on transaction types permissions

To implement a restriction allowing only specific transactions type i.e. POS only restriction, whitelist logic is used to allow transaction with specified transaction types to be approved. The most efficient approach for allowing a limited number of items in large pools of other possibilities is through the application of whitelist logic. This method necessitates the explicit specification of each allowed item in the whitelist, which ensures that transactions involving these specified items are permitted and can be approved.

Name	POS Transaction Types including ATM	Direction
CSD	Cash advance	Debit
CSR	Cash advance Reversal	Credit
RTL	POS Purchase	Debit
RTR	POS Purchase Reversal	Credit
CBN	POS Cash-back	Debit
CBR	POS Cash-back Reversal	Credit
RET	Merchandise return	Credit
RER	Merchandise return Reversal	Debit
CNP	Card-Not-Present (except e-commerce)	Debit
CNR	Card-Not-Present Reversal (except e-commerce)	Credit
CRP	Card-Not-Present return (except e-commerce)	Credit
CRR	Card-Not-Present return Reversal (except e-commerce)	Debit
GAM	Gambling	Debit
GAR	Gambling Reversal	Credit
PRE	POS Pre-authorization purchase	Debit
PRR	POS Pre-authorization purchase Reversal	Credit
QUA	Quasi-Cash	Debit
QAR	Quasi-Cash Reversal	Credit
ATM	ATM withdrawal	Debit
ATR	ATM withdrawal Reversal	Credit
EPA	E-commerce Pre-authorization purchase	Debit
EPR	E-commerce Pre-authorization purchase Reversal	Credit

Comparison of main attributes of Card and CPD

CPD functions as a card configurator for new cards. To understand the entire dynamic, we can take a look at the table below.

CPD	CARD	DIFFERENCES
CPD CODE	CPD code	The same value.
N/A	Card ID	CPD is not defined for a specific card, so CPD does not need this information.
CARD DEFAULT STATUS	Card status	The same value at the time of card creation.
N/A	Cardholder details	CPD is not defined for a cardholder, so CPD does not need this information.
N/A	Account details	CPD is not defined for a specific account, so CPD does not need this information.
CARD PRODUCT PAN (PRIMARY ACCOUNT NUMBER = CARD NUMBER) RANGE	Card truncated PAN	The card has already been assigned a PAN from PAN ranges set by CPD.
CARD ASSOCIATION	Card association	The same value.
CARD TECHNOLOGY (I.E. VIRTUAL, CONTACTLESS, MAGNETIC STRIPE ETC.)	N/A	This information is stored only in CPD.
CARD TYPE (I.E. CREDIT, DEBIT)	Card type (i.e. Credit, Debit)	The same value.
CARD LIMIT RANGES AND RESTRICTIONS	Card limit ranges and restrictions	The card has a list of specific limit amounts and restrictions, and CPD has list of limit ranges and restrictions available to be set by preferences in case CPD allows it, otherwise default values from CPD are used (but only in case of restrictions).
SEGMENT (I.E. RETAIL, CORPORATE ETC.)	Segment (i.e. Retail, Corporate etc.)	The same value.
IMMEDIATE DIGITAL ACTIVATION	Immediate digital activation	The same value.
CARD DEFAULT EXPIRATION	Card validity from and to	The card has exact dates, and CPD has the default number of months.
CARD GRAPHIC DESIGN	Card graphic design	The same value.
CARD DELIVERY TYPE	Card delivery address and type	The card has a specific address to which the physical card is supposed to be delivered. Only the delivery type value matches the CPD value.
OPTION TO HAVE EMBOSSED NAME	Embossed information	The card has information on what is embossed; CPD only knows if it should be embossed and in which style.
AUTORENEWAL	Autorenewal	The same value.
N/A	Block information	The specific block list includes unique block reasons and dates, connected to each individual card.
OPTION TO VIEW/CHANGE PIN	N/A	This information is stored only in CPD.

CPD Code Example

{
  "id": 2,
  "code": "VISA_PHYS_1",
  "name": "VISA Physical Retail",
  "description": "VISA Physical Retail",
  "images": [
    "phys_standard.png"
  ],
  "validFrom": "2023-05-29T00:00:00Z",
  "validTo": "2999-12-31T23:59:59.999Z",
  "associationCode": "VISA",
  "technology": [
    "CONTACTLESS_CHIP",
    "CONTACT_CHIP",
    "MAGSTRIPE"
  ],
  "cardType": "DEBIT",
  "segment": [
    "RETAIL"
  ],
  "status": "ACTIVE",
  "defaultValidity": 48,
  "pan": {
    "length": 16,
    "prefix": "451161",
    "lowerRange": "010000000",
    "upperRange": "019999999"
  },
  "renewalAuto": true,
  "embossNameMaxLength": 21,
  "embossNameCreateMode": "LAST_FIRST",
  "defaultCardStatus": "DIGITALLY_ACTIVE",
  "defaultEcommerceStatus": true,
  "limits": [
    {
      "limitId": "LIM_17_POS_AMT_D",
      "name": "POS transactions",
      "issuerBillingCurrency": "CZK",
      "period": "DAILY",
      "transactionTypes": "CSD,CSR,RTL,RTR,CBN,CBR,CNP,CNR,GAM,GAR,PRE,PRR,MTP,MTR",
      "limitType": "AMOUNT",
      "defaultLimitValue": 50000,
      "maximumLimitValue": 100000,
      "customerCanModify": true
    },
    {
      "limitId": "LIM_17_ECOM_AMT_D",
      "name": "E-commerce transactions",
      "issuerBillingCurrency": "CZK",
      "period": "DAILY",
      "transactionTypes": "ECP,ECR,EGM,EGR,EPA,EPR",
      "limitType": "AMOUNT",
      "defaultLimitValue": 20000,
      "maximumLimitValue": 100000,
      "customerCanModify": true
    },
    {
      "limitId": "LIM_17_ATM_AMT_D",
      "name": "ATM withdrawals",
      "issuerBillingCurrency": "CZK",
      "period": "DAILY",
      "transactionTypes": "ATM,ATR",
      "limitType": "AMOUNT",
      "defaultLimitValue": 50000,
      "maximumLimitValue": 100000,
      "customerCanModify": true
    }
  ],
  "handoverType": [
    "POST",
    "BRANCH"
  ],
  "pinChange": true,
  "pinView": true,
  "embossNameGenerate": true,
  "renewalMonthUpfront": 2,
  "renewalType": "RENEWAL",
  "deliveryTracking": true,
  "persolineCompany": "Card processor",
  "processorCompany": "Card processor",
  "graphics": "41",
  "restrictions": [
    {
      "restrictionId": "TPRF_17_01_2",
      "defaultRestrictionValue": "DISABLED",
      "customerCanModify": true,
      "evaluation": "FLAG",
      "name": "Cash transactions",
      "restrictionType": "TRANSACTION_FLAG"
    },
    {
      "restrictionId": "TPRF_17_01_3",
      "defaultRestrictionValue": "DISABLED",
      "customerCanModify": true,
      "evaluation": "FLAG",
      "name": "Contactless transactions",
      "restrictionType": "TRANSACTION_FLAG"
    },
    {
      "restrictionId": "TPRF_17_01_4",
      "defaultRestrictionValue": "DISABLED",
      "customerCanModify": true,
      "evaluation": "FLAG",
      "name": "Online transactions",
      "restrictionType": "TRANSACTION_FLAG"
    },
    {
      "restrictionId": "TPRF_17_01_5",
      "defaultRestrictionValue": "DISABLED",
      "customerCanModify": true,
      "evaluation": "FLAG",
      "name": "Magstripe transactions",
      "restrictionType": "TRANSACTION_FLAG"
    },
    {
      "restrictionId": "TPRF_17_01_7",
      "defaultRestrictionValue": "DISABLED",
      "customerCanModify": false,
      "evaluation": "FLAG",
      "name": "DCC transactions",
      "restrictionType": "TRANSACTION_FLAG"
    },
    {
      "restrictionId": "TPRF_17_01_9",
      "defaultRestrictionValue": "DISABLED",
      "customerCanModify": true,
      "evaluation": "FLAG",
      "name": "Mobile wallets transactions",
      "restrictionType": "TRANSACTION_FLAG"
    },
    {
      "restrictionId": "TPRF_17_01_8",
      "defaultRestrictionValue": "DISABLED",
      "customerCanModify": false,
      "evaluation": "FLAG",
      "name": "Chip&PIN transactions",
      "restrictionType": "TRANSACTION_FLAG"
    },
    {
      "restrictionId": "TPRF_17_01_6",
      "defaultRestrictionValue": "ENABLED",
      "customerCanModify": false,
      "setting": "7995,7801,7800,7802,5967",
      "evaluation": "BLACKLIST",
      "name": "MCC transactions (no gambling, adult business)",
      "restrictionType": "MCC"
    },
    {
      "restrictionId": "TERMINAL_EU_COUNTRIES",
      "defaultRestrictionValue": "DISABLED",
      "customerCanModify": false,
      "setting": "AUT,BEL,BGR,HRV,CYP,CZE,DNK,EST,FIN,FRA,DEU,GRC,HUN,IRL,ITA,LVA,LTU,LUX,MLT,NLD,POL,PRT,ROU,SVK,SVN,ESP,SWE",
      "evaluation": "WHITELIST",
      "name": "Terminal EU countries",
      "restrictionType": "COUNTRYCODES"
    },
    {
      "restrictionId": "TRANSACTIONS_PERMISSIONS_A",
      "defaultRestrictionValue": "ENABLED",
      "customerCanModify": false,
      "setting": "ATM,ATR,CSD,CSR,RTL,RTR,CBN,CBR,RET,RER,CNP,CNR,CRP,CRR,ECP,ECR,EME,EMR,GAM,GAR,EGM,EGR,CAV,PIN,INQ,PRE,PRR,EPA,EPR,MTP,MTR",
      "evaluation": "WHITELIST",
      "name": "Transactions permissions",
      "restrictionType": "TRANSACTION_TYPE"
    }
  ]
}

Card Code Example

{
  "card": {
    "cpdCode": "VISA_PHYS_1",
    "cpdVersion": 2,
    "cpdId": "2",
    "cardId": 5057,
    "name": "VISA Physical Retail",
    "image": [
      "phys_standard.png"
    ],
    "associationCode": "VISA",
    "cardType": "DEBIT",
    "pan": "4511***5777",
    "cardProcessorId": "777821194",
    "status": "DIGITALLY_ACTIVE",
    "validFrom": "2024-03-01",
    "validTo": "2028-03-01",
    "expressDelivery": false,
    "ecommerceStatus": true
  },
  "holder": {
    "holderExternalId": "1001863",
    "firstName": "Duncan",
    "lastName": "Clarke",
    "embossName": "CLARKE DUNCAN",
    "sex": "MALE",
    "birthdate": "01-01-1970",
    "phoneNumber": "123456789",
    "residenceAddress": {
      "addressLine1": "Boční 300",
      "city": "Jablonec nad Nisou",
      "country": "CZE",
      "zip": "46801"
    },
    "mailingAddress": {
      "addressLine1": "Českomalínská 1037/ 24",
      "city": "Praha",
      "country": "CZE",
      "zip": "16000"
    },
    "knownAddresses": [
      {
        "addressLine1": "Národní 60/28",
        "city": "Prague",
        "country": "CZE",
        "zip": "110 00"
      },
      {
        "addressLine1": "Českomalínská 1037/ 24",
        "city": "Praha",
        "country": "CZE",
        "zip": "16000"
      },
      {
        "addressLine1": "Boční 300",
        "city": "Jablonec nad Nisou",
        "country": "CZE",
        "zip": "46801"
      }
    ]
  },
  "delivery": {
    "deliveryType": "POST",
    "deliveryAddress": {
      "addressLine1": "Národní 60/28",
      "city": "Prague",
      "country": "CZE",
      "zip": "110 00"
    },
    "expressDelivery": false
  },
  "accounts": {
    "accountOwner": {
      "holderExternalId": "1001863",
      "firstName": "Duncan",
      "lastName": "Clarke"
    },
    "accounts": [
      {
        "accountExternalId": "1000019953",
        "accountCurrency": "CZK"
      }
    ]
  },
  "limits": [
    {
      "limitId": "LIM_17_POS_AMT_D",
      "name": "POS transactions",
      "limitValue": 50000,
      "currentLimitValue": 50000,
      "limitType": "AMOUNT"
    },
    {
      "limitId": "LIM_17_ECOM_AMT_D",
      "name": "E-commerce transactions",
      "limitValue": 20000,
      "currentLimitValue": 20000,
      "limitType": "AMOUNT"
    },
    {
      "limitId": "LIM_17_ATM_AMT_D",
      "name": "ATM withdrawals",
      "limitValue": 50000,
      "currentLimitValue": 50000,
      "limitType": "AMOUNT"
    }
  ],
  "blocks": [],
  "restrictions": [
    {
      "restrictionId": "TPRF_17_01_2",
      "restrictionType": "TRANSACTION_FLAG",
      "restrictionValue": "DISABLED",
      "name": "Cash transactions",
      "restrictionValues": [
        "ENABLED",
        "DISABLED"
      ]
    },
    {
      "restrictionId": "TPRF_17_01_3",
      "restrictionType": "TRANSACTION_FLAG",
      "restrictionValue": "DISABLED",
      "name": "Contactless transactions",
      "restrictionValues": [
        "ENABLED",
        "DISABLED"
      ]
    },
    {
      "restrictionId": "TPRF_17_01_4",
      "restrictionType": "TRANSACTION_FLAG",
      "restrictionValue": "DISABLED",
      "name": "Online transactions",
      "restrictionValues": [
        "ENABLED",
        "DISABLED"
      ]
    },
    {
      "restrictionId": "TPRF_17_01_5",
      "restrictionType": "TRANSACTION_FLAG",
      "restrictionValue": "DISABLED",
      "name": "Magstripe transactions",
      "restrictionValues": [
        "ENABLED",
        "DISABLED"
      ]
    },
    {
      "restrictionId": "TPRF_17_01_9",
      "restrictionType": "TRANSACTION_FLAG",
      "restrictionValue": "DISABLED",
      "name": "Mobile wallets transactions",
      "restrictionValues": [
        "ENABLED",
        "DISABLED"
      ]
    }
  ]
}