Programs configurations are defining the behaviour and capabilities of your accounts and the cards linked to them. You can have as many programs as you would like to.
Programs are applied at an account level. During your onboarding will configure your programs and provide you your program codes.
For each account you open, you are required to provide a program code in the API request.
Each program holds account settings and cards settings.
Account Settings
Account settings are defining the behaviour of the account and its balances. You can configure the following attributes:
Currencies – defines the set of currencies that you will have balances for each account you open for this program. For instance, you have defined program 1 with currencies EUR and GBP. When you open an account with program 1 this account will have two balances one with EUR and one with GBP. Important to note is that if you have multiple currencies under one account you won’t be able to link a card to this account.
Generate IBAN – would define if an IBAN should be generated and assigned to the balances of the account. You can configure IBAN generation for each balance currency. For GBP we assign IBAN and account number. Example: you configure program 1 with currencies EUR and GBP and you set the Generate IBAN configuration only for EUR. When you open an account with program 1 it will have two balances an EUR one with an IBAN and a GBP one without IBAN or account number. Important to note is that if you had set the IBAN generation for GBP as well, the platform would generate both IBAN and account number for this balance. Overall, we issue IBANs only for GBP, EUR and BGN.
Generate virtual IBANs – Similar to the Generate IBAN configuration this parameter will define if the platfrom will generate IBANs for the virtual accounts of this program. Example: If in program 1 I have set the that we need to generate virtual IBANs, and I create a virtual account liked to an account of program 1 this virtual account’s EUR balance will have an IBAN and the GBP one won’t have one. You can’t configure virtual IBAN generation per currency as it will inherit what has been configured for the payment account the virtual account is linked to.
Important to note is that consumers can be linked to businesses in case these consumers need to be able to access a particular business account, and they will be treated as an authorized user by the business. A classical use case is an employee to have access to a business payment account for the purpose of covering business expenses.
Card Settings
Are determining the default behaviour of the cards linked to an account of a particular program.
General card settings (cannot be changed via API):
Enable non-personalised cards – would enable issuing of non-personalised cards.
Allow issuing of virtual cards – enables issuing of virtual cards for a program.
Allow issuing of physical cards – enables issuing of virtual cards for a program.
Apple Pay Enable – this would enable the cards linked to accounts with this program to be enabled for Apple Pay push-provisioning.
Google Pay Enable – this would enable the cards linked to accounts with this program to be enabled for Google Pay push-provisioning.
It's important to note that Apple and Google Pay enablement may require additional project with the card schemes and for Apple Pay a lab certification might be required.
Your account program holds your default card settings as well. They will determine the default behaviour of all cards linked to an account of a particular program. These settings can be easily changed for each card via the Card Limits and Groups endpoint:
Usage group – The usage groups define what operations are allowed: ATM withdrawal, POS payment, Online payment, and Cash Advance.
Authorisation fee group – The authorisation fee group defines transaction fees like ATM withdraws,
Recurring fee group – The recurring fee group defines recurring fees like card monthly fee.
Velocity limit group – the default velocity limit group defines the limits of the card for different types of operations.
MCC Whitelists and Blacklists – the MCC whitelist/blacklist as the name suggests are used to allow or forbit different merchant categories.
Acceptor list – the acceptor list defines is a whitelist for the MIDs and TIDs for which transactions would be authorised.
Funds loading
Internal transfers
You can load cards from your funding account or from any other payment account in your instance. Based on your configurations and approved program cards can be loaded by customers sending internal transfers.
Inbound transfer
By receiving inbound transfer to the IBAN or account number of the account linked to the card.
Card/Account to Card
By using the rails of Visa and Mastercard Money Send for sending funds directly from account or card. Refer to Mastercard Send and Visa Direct.