Team and roles
Staff get their own sign-in with a role the software enforces every time, including a refund limit the owner sets — so delegating the counter does not mean handing over the business.
Any business with more than one person: shops with cashiers, schools with a fees desk, cooperatives, NGOs, platforms with a developer who is not an employee.
Part of the platform itself: it is present wherever BitriPay runs.
The problem
Small businesses share one login because the alternative is doing everything themselves. One shared password means no idea who refunded what, no way to remove a leaver, and a settlement account anybody could change.
How it works
- Invite the person by email or phone; they get their own account and sign in as themselves.
- Give them a role: cashier, finance manager, operations manager, developer, read-only, administrator.
- Set the cashier refund limit for the organisation; the software refuses anything above it.
- Every action is written to the audit trail under their name, and removing them takes effect at once.
What you can check
Facts about the running platform rather than adjectives. Each one is visible in the product, the API reference or the ledger.
- A cashier takes payments and refunds up to the organisation’s limit, and is refused settlement instructions, API secrets, statements, customer exports and member management.
- A finance manager changes settlement instructions and refunds above the cashier limit, but never sees API keys.
- A developer manages keys and webhooks and cannot issue refunds; the keys stay with the business when the developer leaves.
- The owner is immutable: the role cannot be removed by anybody, including an administrator.
- Business units can be linked to locations, so a payment taken at a branch carries the unit it belongs to.
What it costs
Included. There is no per-seat charge, and a business can invite as many people as it needs.
Questions
What stops a cashier refunding a sale into their own account?
Two things. A refund returns money to the payer of the original payment, not to an address the cashier chooses; and a cashier may only refund up to the limit the business sets, above which the refund is refused and has to be made by someone with the authority.
An employee has left. What do I have to change?
Remove them. It takes effect at once, and their past actions stay in the audit trail under their own name. No password has to be changed, because they never had yours.
My developer is not an employee. Can I give them access safely?
Give them the developer role. They manage API keys and webhooks and can create payments, but cannot touch settlement, payouts or customer exports. Every action is attributed to them, and the keys stay with your business after they go.
Read next
Point of sale
A till that runs on the phone already in the shopkeeper’s hand, with line items and VAT, and no hardware to buy, charge or replace.
Connected accounts
Create your customers’ merchant accounts by API, take payments for them with your own key, keep your fee — and hand the account over whenever they are ready, keys and history intact.