Good to see you, there ✳
Here is what is happening with your customer wallets.
Transaction activity
Ledger entries per day over the last 7 days
EUR wallets
Limits that protect your customers and keep you within closed-loop rules.
Recent transactions
The latest wallet activity.
| TRANSACTION | CUSTOMER | DATE | AMOUNT | TYPE |
|---|
Customer wallets
Wallets are created through the API when a customer first uses your shop.
| CUSTOMER | CUSTOMER ID | BALANCE | STATUS | LAST ACTIVITY |
|---|
Transactions
Every top-up, charge and refund. The ledger is append-only.
| TRANSACTION | CUSTOMER | REFERENCE | DATE | AMOUNT | BALANCE AFTER | TYPE |
|---|
API keys
Connect your shop's server to Kassara.
Secret key
Use it from your server only, as Authorization: Bearer sk_test_…. Never put it in browser code.
Webhooks
Kassara POSTs a signed JSON event to your server when a top-up succeeds, a wallet checkout is paid, or a charge or refund is made. Verify the Kassara-Signature header with your signing secret (see the docs).
| Event | Status | Attempts | Sent | |
|---|---|---|---|---|
| No events yet. | ||||
One active key
Generating a new key revokes the old one straight away. We only store a hash, so a lost key can't be recovered.
Your plan
Usage this month and your estimated Kassara bill.
Change plan
Upgrades start immediately. Downgrades start on the 1st of next month.
Payment-processing fees are separate and charged by your payment provider. Starter top-up fees are paid by the customer on top of the top-up; the wallet is credited with the top-up amount only.
Proposed launch prices, test mode. Top-up volume allowances for Business and Business Pro are not final yet; your volume is tracked in the meantime. No real money is billed.
Settings
Your business details and wallet limits.
Closed-loop by design
Each wallet belongs to one business. Balances can't move between merchants or be withdrawn as cash.
Account details
—