Wallet tokenisation
Phone-wallet payments use device tokens, never the real card number.
The questions worth asking before connecting any financial product to your company. The answers are below, including the unwelcome ones.
Your balance is exactly where it was. Every error screen names the state of your money rather than showing a generic apology. If a transaction left but was never confirmed it sits in a reconciliation queue, you are told which state it is in, and it is resolved rather than left hanging.
The company is verified and every individual holding spend or payout rights is identified before first use. There is no guest tier and no way to skip it; verification happens in one flow covering the business, its owners and its users.
We keep legal entity records, beneficial ownership, the results of verification, and transaction history. Full card numbers are never stored. Identity numbers are kept only as salted hashes, because the plaintext has no use after the check is done.
Owners, finance staff, members and read-only viewers. A payout can require a second approver before it leaves. Every action carries the identity of the person who did it into an append-only log that cannot be edited or deleted.
A new workspace opens with conservative limits. They grow as the account builds a record, not as it asks. A limit is a risk bound for the seconds before a transaction clears, not a judgement about the company.
Phone-wallet payments use device tokens, never the real card number.
Required to approve payments and sensitive changes.
Least privilege by default, second approver on payouts.
Freeze any card, user or the whole workspace from the dashboard.
Every outgoing payment is announced by push and email.
TLS 1.3 in transit; AES-256 at rest with key rotation.
Ledger and audit log entries can never be altered or deleted.
Daily reconciliation with a target difference of zero.
One work email. We reach out when your region and use case are ready.