Technical index
The capability map
35 capabilities across 14 domains. 25 carry operations, 10 are planned and named here because they are not yet available. State is drawn as length, never as colour — colour is the tenant variable in a white-label portal, so it cannot also carry meaning.
Cards
Track a card application from submission to the card being produced.
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.
Create individual, corporate and virtual cards, and check which products a customer is eligible to hold before you issue.
Move a card through its states after issuance — status changes, replacement, renewal, blocking and closure.
Issue and activate pre-produced cards that carry no embossed name, then bind one to a customer at the point of sale.
Customers and accounts
Move a customer or a card between branches, and read the cards a branch holds.
Read the customer behind the cards — portfolio summary, corporate relationships and total assets.
Attach and detach the accounts a card draws on, and read back what a card is currently linked to.
Transactions
Draw cash against a credit line, and cancel an advance before it settles.
Read what happened on a card and correct it — transaction history, pending provisions, reversals and slip receipts.
Limits and controls
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.
Cap what a card may do per transaction, per day, per week and per month, by channel and operation type.
Turn individual capabilities on and off for a card — e-commerce, international use, mail order and other miscellaneous options.
Instalments
Split a purchase or a cash advance across a repayment schedule, then track, settle early or cancel the plan.
Billing and statements
Follow up arrears — delinquency state, collection detail and the legal process behind an unpaid balance.
Take a payment against card debt, check a card is eligible to be paid down, and cancel a payment that should not have run.
Close a card balance ahead of its normal cycle.
Documented but empty — needs a decisionNo operation is assigned to this capability. Either it closes, or it is re-declared planned with a note saying what the platform does not yet expose.
Produce the statement a cardholder reads, and manage the period, delivery preference and address behind it.
Security
Set and change a PIN, manage the try counter, and generate or verify the card verification values.
3-D Secure enrolment and authentication for card-not-present transactions.
Documented but empty — needs a decisionNo operation is assigned to this capability. Either it closes, or it is re-declared planned with a note saying what the platform does not yet expose.
Disputes
Open a dispute against a transaction, attach the evidence, and cancel a case that should not have been raised.
Fraud
Raise, read and report fraud against a card or a transaction.
Not yet availableNine fraud operations exist, all inside the dispute integration service — Mastercard FDA fraud states, issuer fraud lists and fraud record creation. That API is `publish: false` because its own documentation describes a different service, so none of them is reachable yet. Publishing it is a content problem, not a code one.
Clearing and settlement
Scheme file processing, reconciliation and the end-of-day settlement position.
Not yet availableFive clearing operations exist in the dispute integration service, which is not published. The business flow behind them is documented — see the clearing and settlement guide — but the endpoints are not yet reachable.
Wallets
Provision a card into a digital wallet and manage it once it is there.
Not yet availableNo 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
Read the reward and campaign periods a customer's cards qualify for.
Platform
ATM acquiring, terminal management and the cash operations behind them.
Not yet availableATM 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.
How a scheme's ISO 8583 message becomes the JSON these APIs speak, field by field.
Not yet availableThe conversion happens inside the platform and is not itself exposed as an API. What can be published today is the field mapping, which is documented from the message structures rather than from an endpoint.
The operations a call centre agent performs on a cardholder's behalf, and the IVR behind them.
Not yet availableNo 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.
Not yet availableInstalments 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.
Look up the reference data a card programme is configured against — products, codes and parameters.
Replace a PAN with a token for wallet provisioning, card-on-file and network tokenisation.
Not yet availableNo endpoint in these seven APIs issues, reads or de-tokenises a payment token. The only `token` operations on the platform belong to the OAuth2 security token service, which is a different thing entirely.
Monitoring and reporting
The metrics the platform emits, and the dashboards built on them.
Not yet availableEverest emits OpenTelemetry metrics that Prometheus scrapes and Grafana draws. The metric families are documented from the framework; this deployment's dashboard inventory is not yet confirmed.
The events the platform publishes, and the topics other systems subscribe to.
Not yet availableEverest publishes events over Kafka, RabbitMQ, NATS and HTTP through a common consumer interface. The transport is documented from the framework; this deployment's topic list is not yet confirmed.