Capability map
What the platform does
35 capabilities across 14 domains — one business function each, implemented once per card programme. 23 carry operations between them, 4 are named here because they are not available yet, and saying so is the point: an absence a bank can see changes a scoping decision, one it cannot see does not.
Open one to see what it is for, which journeys walk through it and every operation it binds. For how to call them, start at Get started.
35 capabilities · 383 bound operations
Cards 5
Track a card application from submission to the card being produced.
- credit
- debit
- prepaid
Get a produced card to the cardholder — generate the distribution file, track the courier by barcode, and correct the delivery address while the card is in transit.
- delivery
Create individual, corporate and virtual cards, and check which products a customer is eligible to hold before you issue.
- credit
- debit
- prepaid
Move a card through its states after issuance — status changes, replacement, renewal, blocking and closure.
- common-methods
- credit
- debit
- prepaid
Issue and activate pre-produced cards that carry no embossed name, then bind one to a customer at the point of sale.
- credit
- debit
- prepaid
Customers and accounts 3
Move a customer or a card between branches, and read the cards a branch holds.
- credit
- debit
- prepaid
Read the customer behind the cards — portfolio summary, corporate relationships and total assets.
- common-methods
- credit
- debit
- prepaid
Attach and detach the accounts a card draws on, and read back what a card is currently linked to.
- common-methods
- credit
- debit
Transactions 2
Draw cash against a credit line, and cancel an advance before it settles.
- credit
Read what happened on a card and correct it — transaction history, pending provisions, reversals and slip receipts.
- common-methods
- credit
- debit
- prepaid
Limits and controls 3
Raise, lower and reverse the spending limit on a card or on the customer behind it. Every change returns a log id you can reverse with.
- common-methods
- credit
- debit
Cap what a card may do per transaction, per day, per week and per month, by channel and operation type.
- credit
- debit
- prepaid
Turn individual capabilities on and off for a card — e-commerce, international use, mail order and other miscellaneous options.
- common-methods
- credit
- debit
- prepaid
Instalments 1
Split a purchase or a cash advance across a repayment schedule, then track, settle early or cancel the plan.
- credit
Billing and statements 4
Follow up arrears — delinquency state, collection detail and the legal process behind an unpaid balance.
- common-methods
- credit
Take a payment against card debt, check a card is eligible to be paid down, and cancel a payment that should not have run.
- common-methods
- credit
Close a card balance ahead of its normal cycle.
Produce the statement a cardholder reads, and manage the period, delivery preference and address behind it.
- common-methods
- credit
Security 2
Set and change a PIN, manage the try counter, and generate or verify the card verification values.
- common-methods
- credit
- debit
- prepaid
3-D Secure enrolment and authentication for card-not-present transactions.
Disputes 1
Open a dispute against a transaction, attach the evidence, and cancel a case that should not have been raised.
- credit
Fraud 1
Raise, read and report fraud against a card or a transaction.
Clearing and settlement 1
Scheme file processing, reconciliation and the end-of-day settlement position.
Wallets 1
Provision a card into a digital wallet and manage it once it is there.
No endpoint in this corpus provisions a card into Apple Pay, Google Pay, Samsung Pay or a bank's own wallet. Wallet provisioning depends on tokenisation, which is also not yet exposed.
Rewards 1
Read the reward and campaign periods a customer's cards qualify for.
- common-methods
- credit
Platform 8
ATM acquiring, terminal management and the cash operations behind them.
ATM appears in this corpus only as a limit field on a card and as a dispute case type. No endpoint drives a terminal or an ATM transaction.
Get a bearer token. Every other call on this portal needs one first.
- oauth2
How a scheme's ISO 8583 message becomes the JSON these APIs speak, field by field.
The operations a call centre agent performs on a cardholder's behalf, and the IVR behind them.
No endpoint here is scoped to an agent or a call. The card operations an agent would use exist, but nothing carries agent identity, call reference or the authentication a call centre journey needs.
Consumer lending beside the card — origination, schedule and repayment.
Instalments split a card transaction across a schedule; that is documented and real. A loan product with its own origination and account has no endpoint in this corpus.
Health checks and cache refresh. Called by your monitoring, not by a cardholder journey.
- common-methods
- credit
- debit
- delivery
- oauth2
- prepaid
Look up the reference data a card programme is configured against — products, codes and parameters.
- common-methods
- credit
- debit
- prepaid
Manage payment tokens against the token service provider — suspend, resume, delete, look up and search, and keep the provider in step when the card changes.
Monitoring and reporting 2
The metrics the platform emits, and the dashboards built on them.
The events the platform publishes, and the transports that carry them.
How to read the stateFour states — documented, drafted, planned, on request — drawn as length rather than as colour, because colour is the tenant variable in a white-label portal and cannot also carry meaning. A planned capability legitimately holds nothing; a documented one that holds nothing says on its own page why.