The card layer for teams that spend online.
Issue virtual and physical cards across 30+ BINs, cap what each one can spend, and read every subscription, ad account and API bill in a single ledger — for your designers, your buyers, and now your agents.
Two halves of one account
Issuing on one side, money and reporting on the other — one login, one ledger.
Cards with real-time controls
Virtual in seconds, physical when the spend needs plastic. Choose a shared BIN or take a dedicated range, set the authorisation rules, and freeze or revoke without losing history.
One balance, many budgets
Hold funds at the account level and let every card draw from it. Split by entity, client or campaign, and close the month from the dashboard instead of a spreadsheet.
Who runs on sudu
Subscriptions that never fail
One card per tool — Figma, Adobe, fonts, stock — so a single renewal can never take down the whole stack.
A card per ad account
Issue in bulk, top up mid-flight at 2am, and keep Google, Meta and TikTok budgets separated to the transaction.
Client spend, ring-fenced
Roles, per-card caps and client tags across several entities. Freeze the day a contractor leaves; export the month in one file.
Cards inside your product
Issue, fund and freeze through the API under your own brand — the same rails, on your side of the login.
The whole month on one screen
Balance, cards, caps and the live feed — no export required to answer “where did it go”.
What changes in the first week
From sign-up to first charge
Register and verify
Minutes as an individual, a little longer as a company. One review, then the account is live.
Fund the balance
Hold USD or EUR at the account level; internal transfers to cards clear instantly, any day.
Issue with rules
Name it, cap it, assign it to a person, a client or an agent. Usable the moment it appears.
Watch the ledger
Authorisations, declines and refunds in one feed — by card, merchant, entity and month.
Questions before you register
Anything else — support answers in chat, not in a ticket queue.
Do top-ups clear on a Sunday night?+
Yes — moving money from your balance onto a card stays inside sudu, so it lands in seconds regardless of the hour, the weekend or the bank holiday. The only requirement is a funded balance.
We run three brands. Can they share one account?+
They can. Each brand keeps its own balance, cards, permissions and statements, and you switch between them from a single login instead of juggling three sets of credentials.
What does “AI-agent ready” actually mean?+
Your automations get their own cards through the API — scoped to a budget, a merchant allow-list and an expiry date, with webhook events per authorisation and instant revoke. No agent ever holds a human's card details.
Shared or dedicated BINs?+
Both. Start on a shared BIN and move to a dedicated BIN or range as volume grows — with the same API and dashboard.
How many cards can I issue?+
As many as the work needs — per tool, per ad account, per client, per agent. Freezing and reopening keeps the card's history intact.
How are funds and data protected?+
Cards and balances sit with licensed third-party issuers and their partner banks, not with us — Sùdù Limited is not a bank. Card data is handled under PCI DSS, payments carry 3-D Secure, and access to the dashboard is governed by roles and per-card permissions.