Karizma One Pay: payment accounts and cards, in the same system as your management
The financial brick of the platform. It rests on Karizma's payment agent status, which allows payment accounts to be opened and cards to be issued for your company and your employees — with no cap on the number, and without leaving your ERP.
Payment belongs in the same system as management
Your ERP knows what has to be paid; your bank knows what has been paid. In between: exports, imports, reconciliations, and a permanent gap between what the books say and what the account says.
Karizma One Pay removes the in-between. The account, the cards, the expenses and the accounting entries are the same object in the same system. There is no reconciliation left to do, because there is nothing left to reconcile.
Six functions, one interface
Select a function for the detail.
Payment accounts
Accounts dedicated to your company, with their own bank identifier, usable both to collect and to pay.
- One account per group company
- Collection and payment
- Opening driven from the platform
- Balance visible in the dashboard
- Full, exportable history
- No forced change of bank
Cards for your employees
Cards issued on demand, individually or per department, with no cap on the number. A new card is no longer a file: it is a click.
- Immediate issuance
- Physical or virtual depending on use
- Assigned per person, department or project
- Blocked from the platform
- No cap on the number of cards
- Individual spend tracking
Limits and spending rules
Your spending policy stops being a document and becomes a rule that applies at the moment of payment.
- Limit per card and per period
- Restriction by expense category
- Restriction by supplier or country
- Manager approval above a threshold
- Blocked upfront, not audited afterwards
- Changes apply immediately
Receipts attached
The employee photographs the receipt; it is attached to the expense and to the accounting entry. No more chasing paperwork at closing.
- Capture from mobile
- Automatic attachment to the transaction
- Automatic reminder when missing
- Archiving with evidential value
- Search by amount, date or supplier
- Export for the auditor
Automatic reconciliation
Every transaction is attached to its accounting counterpart at the moment it happens. Bank reconciliation stops being a month-end task.
- Entry generated at the instant of payment
- Automatic invoice matching
- No statement import
- Discrepancies flagged immediately
- Faster closing
- Complete audit trail
Multi-entity and multi-currency
Several companies, several accounts, a consolidation that holds. The exact currency scope is set during scoping.
- One account per entity
- Differentiated rules per subsidiary
- Real-time consolidation
- Inter-company recharging
- Reporting per entity and consolidated
- Currency scope set at scoping
The framework: payment agent status
This status is what makes the brick possible. It authorises Karizma to open payment accounts and issue cards for its customers, within a regulated and traceable framework — where a conventional software vendor can only connect to a third-party bank.
Karizma One Pay is not a bank and does not replace your corporate bank. It is a payment brick operated under payment agent status, designed to carry day-to-day operational flows — employee expenses, supplier payments, collections — as close as possible to your management system. The exact scope, limits and required documents are established during scoping.
What it changes in practice
The same management month, before and after.
| Situation | Without a payment brick | With Karizma One Pay |
|---|---|---|
| A card for a new employee | Bank request, paperwork, several days | Issued from the platform, immediately |
| Checking a spending limit | Afterwards, on the statement | Upfront: the rule blocks at payment time |
| Receipt for an expense | Chasing the employee at month end | Attached to the transaction as it happens |
| Bank reconciliation | Export, import, manual matching | Moot: the entry and the transaction are one object |
| Cash visibility | Bank balance checked outside the ERP | In the dashboard, next to everything else |
| Monthly closing | Days of reconciliation and chasing | Payment entries are already receipted |
Four situations where the difference shows
Employee expenses
One card per person, a limit per internal policy, a receipt photographed on the spot. The expense claim disappears as a process.
Supplier payments
The payment leaves the same system as the invoice that triggered it, with the full audit trail — invoice, approval, payment, entry.
E-commerce collection
Your store deployed from Karizma One collects into an account attached to the same system as stock and accounting.
Multi-entity groups
One account per company, cards per subsidiary, differentiated rules — and a consolidation that does not wait for month end.
From request to first card
Scoping
30 minutes to qualify your structure, volumes, card needs and spending rules.
File
Onboarding file: company documents, beneficial owners, authorised signatories.
Opening
Payment accounts opened and wired to the existing management system.
Cards & rules
Cards issued, limits and rules configured, then assisted go-live.
Control, security and audit trails
A financial brick is judged as much on what it prevents as on what it enables.
Separation of duties
Requesting, approving and paying are three distinct rights. The rule is carried by the platform, not by team habit.
Blocked upfront
An exceeded limit or a forbidden category blocks the transaction at payment time, not at audit time.
Complete audit trail
Every transaction keeps its origin, its approver, its receipt and its accounting entry. That is what an auditor asks for.
Karizma One Pay: your questions
Is Karizma One Pay a bank?
No. It is a payment brick operated under payment agent status. It allows payment accounts to be opened and cards issued to carry your operational flows, and it does not replace your corporate bank or your financing.
How many cards can I issue?
There is no cap. One card per employee, department or use case is a management choice, not a technical constraint.
Do I have to leave my current bank?
No. Karizma One Pay carries day-to-day operational flows and coexists with your existing bank accounts.
How do transactions reach accounting?
They do not «reach» it: they are already there. The payment transaction and the accounting entry are the same object in the same system, which removes statement imports and manual matching.
Can limits be set per employee?
Yes. Per card, per period, per expense category or per supplier. Rules apply at payment time and block non-compliant transactions.
What happens when an employee leaves?
Their card is blocked from the platform, immediately. Past transactions remain traced and attached to their receipts.
What documents are needed to open an account?
The usual onboarding documents: company records, identification of beneficial owners and authorised signatories. The exact list is given during scoping.
Does Karizma One Pay work outside Morocco?
Karizma supports customers in more than 20 countries. The geographic scope and the currencies applicable to your situation are confirmed during scoping.
Is payment mandatory to use Karizma One?
No. It is a brick of the platform, not a condition. You can use the infrastructure, DevOps, connectors and business solutions without activating it.