CreditPartner required

Cards for your customers, with controls they'll use.

Virtual and physical cards with controls. Issues once a processor is connected.

Partner required. The engine is built, and it moves no money until a processor is connected. Tell us about your volumes and we'll tell you where that stands.

Illustrative
Why it matters

What it will change.

Customers want a card for online subscriptions, travel and shops that don't take transfers. Issuing one usually means a long programme with a processor and a separate system to manage it.

Card issuing on Bridge has the whole lifecycle built: card programmes, virtual and physical cards, activation and PINs, spend controls, freezes, digital wallet tokens, authorisations, clearing, refunds and disputes, all posted to the same ledger as the customer's account.

It will issue cards once an issuing processor is connected. Until then, no card can be issued. Tell us your volumes and we'll tell you where that stands.

How it works

Step by step.

  1. Define a programme

    Card types, limits and who can hold one.

  2. Request and activate

    Virtual cards at once; physical cards delivered, activated and given a PIN.

  3. Set controls

    Online, abroad and ATM switches, merchant locks, single-use cards and limits.

  4. Authorise and clear

    Purchases authorised against the customer's account, cleared and posted to the ledger.

  5. Handle the rest

    Refunds, reversals, lost cards, reissues and disputes.

What it will do

Built in, not bolted on.

Virtual and physical

Virtual cards will be issued at once; physical cards delivered and activated.

Controls customers use

Online, abroad and ATM switches and limits the customer can change themselves.

Freeze and unfreeze

A misplaced card frozen in a second, and unfrozen when it turns up.

Single-use and merchant-locked

Cards for one payment, or for one merchant only, for subscriptions and trials.

Digital wallet tokens

Cards added to a phone's wallet, with the token managed on the same record.

Disputes

Raise, represent and track a dispute through to its deadline.

  • Virtual and physical card lifecycle
  • Controls, limits and freezes
  • Disputes and wallet tokens
Use cases

How businesses could use it.

Illustrative businesses, not customers. Figures are made up to show the flow.

A neobank for young professionals in Lagos · Fintechs & neobanks

Virtual cards for online subscriptions

Customers pay for streaming, software and online courses with cards from other banks, so the money leaves the neobank's account every month.

  1. Customers will create a virtual card in the app
  2. Online spending will be on and spending abroad switched on only when they need it
  3. A monthly limit will cap what subscriptions can take
  4. A merchant-locked card will stop a free trial turning into a charge they didn't want

Customers will keep subscriptions on their own account, with controls that stop surprises.

Illustrative

A logistics company with drivers across the South-West · Payroll & HR platforms

Expense cards for field staff

Drivers pay for fuel and tolls with cash advances, and finance spends days matching receipts to advances.

  1. Each driver will get a physical card with a fuel-and-tolls limit
  2. Spending abroad and ATM cash will be switched off
  3. Every transaction will post to the company's ledger as it happens
  4. A card will be frozen the moment a driver leaves

Finance will see every fuel purchase as it happens, without cash advances or receipts to chase.

Illustrative

A digital bank for frequent travellers in Abuja · Fintechs & neobanks

A card for spending abroad

Customers travelling for business carry cash or use cards with poor controls, and fraud abroad is hard to stop.

  1. A customer will switch on spending abroad before a trip
  2. Purchases in another currency will be authorised against their account
  3. A lost card will be reported and replaced, with a new number
  4. A disputed charge will be raised and tracked to its deadline

Customers will travel with a card they control, and a lost card won't ruin the trip.

Illustrative
What it won't do

Honest limits.

  • It issues no cards until an issuing processor is connected.

Questions about card issuing

Can we issue cards today?

Not yet. The issuing engine is built; it will issue cards once an issuing processor is connected.

Which card schemes will be supported?

That depends on the issuing processor. We don't name schemes until one is connected.

Will customers be able to add cards to their phone's wallet?

The engine manages wallet tokens; availability will depend on the processor and the wallet.

Bridge for Business

Tell us what you're building.

We'll come back with what's live for you today, and what's next.