Instant issuance
Branch-counter and self-service kiosk flows, from request to card in hand.
Tala Issuing Platform
Ninety seconds. Card in hand.
Tala is the EMV-grade instant issuance platform for banks and fintechs — from card stock to chip personalisation to a card in your customer's hand, at the branch counter or a self-service kiosk.
90 s
request to card in hand — minutes, not weeks
8 stages
personalisation pipeline
2 channels
branch counter + self-service kiosk
1 platform
SaaS or on your own metal
01Pipeline
Eight stations. One sweep.
Every card takes the same escapement — request to hand-over — driven as one supervised pipeline. A step that needs to retry makes the job wait; it never makes the job fail.
-
T+00:00.0
ST/01
Request
A branch teller or a kiosk customer opens the job. Product, artwork and PIN policy are already configured — and test-verified.
-
T+00:05.0
ST/02
Fund & bill
The job is funded and billed up front — tenant or branch billing, with kiosk payments confirmed synchronously.
-
T+00:12.0
ST/03
Fetch data
Cardholder data is fetched from your bank's middleware over a validated, receipt-gated connection.
-
T+00:24.0
ST/04
Prepare data
Raw records are prepared for personalisation — formatted, checked, and encrypted at rest.
-
T+00:47.0
ST/05
Encode chip
EMV chip personalisation, with keys that never leave the HSM boundary.
-
T+01:04.0
ST/06
Encode magstripe
Magnetic stripe encoding follows on the same device pass.
-
T+01:18.0
ST/07
Print & emboss
Artwork, text and embossing rendered at the branch printer or the kiosk.
-
T+01:30.0
ST/08
Hand over
The card lands in your customer's hand. Anything left over resolves behind a recovery case — never a failed job.
02Platform
The full lifecycle, under one crown.
From card stock to billing, every discipline of issuance is a first-class complication of the platform — not an integration bolted on afterwards.
Inventory & card stock
Purchase, dispatch and load orders, with per-branch tracking of every card.
Card products & schemes
Artwork, EMV profiles and PIN policy — held to test-verified configurations.
Keys & PIN security
HSM key ceremonies, secure PIN pads and PIN-block translation, end to end.
Fleet management
Printers, kiosks and PIN pads — provisioned, monitored and self-healing from the cloud.
Billing & recovery
The card is the expensive artefact — nothing downstream fails the job. Disputes resolve behind recovery cases.
03Hardware
Three instruments in the field.
Branch printers, self-service kiosks and encrypting PIN pads — provisioned, monitored and self-healing from the cloud.
Branch printer
Connectify
Counter-side card printers, managed by the Connectify branch service.
Self-service kiosk
Connectly
Connectly kiosks issue cards end-to-end, without a teller in the loop.
Secure PIN pad
Pinny
Pinny encrypting PIN pads capture customer-selected PINs at the branch or the kiosk.
04Fleet
One barrel drives every hand.
A single branch service manages all of a branch's printers — authored at head office, provisioned from the cloud, recovered in one act. Nothing is set up printer by printer.
One service, many printers
The Connectify branch service drives every counter printer in the branch over one authenticated connection. A kiosk pair drives its own.
Printer-server model
Authored at head office
Printers are registered, configured and approved centrally. The branch receives a sealed configuration and activates once.
Central authoring · workflow approval
Recovered in one act
A rebuilt branch server takes its roster back from the console; every enabled printer is re-proved before the file is kept.
Download · Recover
Verbs that follow the device
Reconnect, retry, disable, enable or remove a printer from the branch console — each answered in a sentence that names the device.
Stateful remote verbs
Kiosks and PIN pads follow the same model — provisioned, allow-listed and bound to the machine that holds them.
05Security & trust
Engineered to be inspected.
EMV-grade issuance is a security discipline first. Keys live in hardware, channels are sealed, and our certificates are published for you to verify.
HSM-backed keys, end to end
Every key ceremony runs inside a hardware security module; keys never leave the HSM boundary.
Thales payShield 10K · SafeNet ProtectServer
Encrypted device channels
Sensitive traffic to printers, kiosks and PIN pads travels over authenticated, encrypted channels.
AES-256-GCM
Reference-token authentication
Every API call is authorised by server-side introspection — tokens are revocable, never self-validated.
OAuth2 reference tokens
Per-tenant PKI
Each tenant operates under its own certificate authority, with revocation lists published in the open.
Published CRLs
Integrations prove themselves
Your middleware proves it is a genuine, unrevoked consumer before each session; working calls carry a short-lived receipt, never a static key.
Preflight handshake · receipts
Validated before it serves
A data-loader or billing connection serves nothing until a live fetch, hold, release and charge have passed. Editing it resets the pass.
Live validation gate
06Deployment
One platform, two homes.
Run on our multi-tenant SaaS, or take the same platform onto your own infrastructure. Moving between them is a switch, not a rewrite.
talaissuing.com
Multi-tenant SaaS
Issue from day one on the hosted platform. We run the metal, patch the fleet services and keep the movement wound; you configure products and issue cards.
Your infrastructure
Self-hosted, on your own metal
The identical platform deployed on-site — your data centre, your HSMs, your network perimeter. Same pipeline, same consoles, same hardware fleet. Your own identity server signs your people in once, everywhere, and federates to the platform for licensing alone.
Same platform either side — a switch, not a rewrite.
07Service
Kept wound.
Branch devices update themselves from a signed feed; estate servers update by hand, on your schedule. A release reaches stable only when two engineers agree.
Signed, verified, staged
A device verifies the feed and the package before anything is staged, waits for an idle window, asks the platform, then installs and reports back.
Signed feeds · verified packages
Two people to go stable
One engineer publishes to pilot; a second approves for stable after a soak. One person never ships alone.
Pilot → stable · dual control
Rings, thresholds, halts
Each tenant rolls a version out in rings on its own dates; a plan halts itself when failures cross the threshold.
Rollout plans
Withdrawn in one act
A bad version leaves every channel at once, every plan targeting it halts, and the people who need to know are told.
Withdraw · notices
Every component ships with a configurator that validates its answers live before it commissions the service.
08First card
A proven movement, fitted to your case.
A working configuration travels as a template — what to do, never whose keys or cards — and becomes your own test configuration on import.
From the library
Start from a configuration that already issues
Scheme applications, data preparation and personalisation profiles, exported from a proven tenant with every identity stripped. The exporter refuses a file that would carry one.
Into your tenant
Bound to your own cards and keys
On import the template is re-bound by name to your products, scheme applications and key roles, hash-checked at every hop, and lands as a test configuration to verify before it goes live.
Knowledge travels; identity never does.
09Begin
Set the movement running.
See a card issued in minutes, not weeks — book a live demonstration with the Digitalley team.