Implementation / Wallet / Card


How does your platform ensure that implementation/agency partners can efficiently delivery digital experiences without excessive development effort and time?
Agency needs to consume the published APIs. In addition, if there is a need, we can do working sessions with developers to speed up the integration.

How does client differ from customer?
A client can be any service provider which provides a service to customers.

A customer is someone who buys a service from a client.

Can customer details be the business details?
Yes, customer details can be the business details.

Is there a testing environment for the API?
Yes, there are sandbox environments, detailed in the API docs.


Does wallet represent the client funds?
Yes, the wallet represents client funds.

Is one card equal to the one wallet?
No, a single wallet can have multiple cards.

How does balance transfer and different currencies work within wallet?
Hierarchy is: client > customer > wallet > card.

A wallet can store multiple currency balances.

Balance transfer works for moving balance from one currency to another currency within the same wallet.


How is card activation usually done?
In theory, it can happen anytime.
Virtual cards are already VIRTUAL_ACTIVE and can be used for e-commerce transactions immediately.

No activation needed.
Physical cards can be activated instantly, but customers are strongly encouraged to activate after cards are delivered.

How do customers know their PIN in the first place?
Each customer needs to use the Change PIN endpoint to set their PIN.

What is required to be live with virtual cards?
Currently, virtual cards can go live.

Do virtual cards need to be activated?
No, virtual cards are VIRTUAL_ACTIVE when issued and should not be activated again.

Our wallet supports multiple currencies. If one currency runs short, then the base currency will be used to clear the transaction.