Custody, conversion and the compliance around it
The crypto module is injected into the customer and merchant account pages rather than living somewhere else, so the balance, the history and the controls sit where the rest of the account already is.
In the account, not beside it
The crypto module appears on the customer and merchant account pages themselves. An operator looking at an account sees the digital asset balances in the same place as the fiat ones, which is the difference between answering a support question in one screen and three.
The wallet it sits inMulti-asset balances
Hold balances across the assets your programme supports, with deposits, conversions and transfers each recorded as their own movement. Every action leaves a history entry, so the question of how a balance got to its current number always has an answer.
How balances are recordedConversion between assets
Convert between digital assets and into fiat, with the movement landing in the same ledger the rest of the platform reads. That keeps a customer moving value between forms of money inside one account rather than withdrawing from one product to fund another.
Currency conversionBuilt for regulated custody
Custody sits with the provider you connect, assigned per programme with its own credentials, in a regulated wallet environment. Beneficiary management applies to digital assets the same way it applies to bank payouts, so sending somewhere new is a decision rather than a text field.
Compliance postureTravel rule
Infrastructure for travel rule reporting is in place against the connected verification provider, so transfers that need originator and beneficiary information can carry it. Talk to us about your specific obligations, because the answer depends on your licence and your corridors.
Identity verification
