For teams and companies
Every card your company owns,
in one place.
Your branding on every card, one panel to manage them, and an API so your HR system can create and suspend cards without anyone opening a browser.
The bit that actually costs money
Every reprint
One promotion, one office move, one new number, and the whole box is waste.
Every leaver
Their card keeps working, with your logo on it, for as long as they keep it.
Every design
Two people order separately and you have two versions of your brand in the wild.
None of those are printing problems. They are all the same problem: the details are on the card instead of behind it.
What a company account does
One panel for every card
See every card your company owns, who has it, and whether it is active.
Import the whole team at once
Upload a CSV. Headers are matched loosely, it previews before writing, and it reports the exact row of anything it could not read.
Your brand, not ours
Your logo, your colours, your card design. No 'powered by' on your card.
Someone leaves on Friday
Suspend their card that afternoon. It stops working on the next tap, wherever the physical card is.
Your fields, not just ours
Define what a card shows — employee ID, branch, membership number, an investment breakdown. Rows in your account, not a change request to us.
Connect it to your systems
REST API and webhooks, so your HR system stays the source of truth and cards follow it automatically.
Connect it to what you already run
Your HR system stays the source of truth. Cards follow it. You can read the whole API before you buy anything.
POST /api/v1/profiles
Authorization: Bearer sk_live_…
Idempotency-Key: 4f3c…
{
"first_name": "Nusrat",
"last_name": "Jahan",
"external_ref": "EMP-1042",
"company": "Your Company Ltd",
"links": [
{ "type": "whatsapp", "label": "Office", "value": "8801XXXXXXXXX" }
]
}Send it twice, safely
An idempotency key means a timed-out retry updates the same person instead of printing a second card.
Webhooks back
Signed, retried for a day, and replayable from your panel when you fix your endpoint.
Clients, not just docs
OpenAPI schema, Postman collection, and generated Python and TypeScript clients.
Full documentation, worked examples and your credentials are in your panel once you have an account.
Team packages
Per card, paid once. Not per user, per month.
Ordering a large batch? Tell us how many and we will quote it — including the delivery date, which matters more than the price when you have an event to be ready for.
Tell us about your team
How many people, what the cards need to show, and when you need them.