One card platform. Multiple issuers.
Bastion separates the customer card model from the underlying card processor. Changing or adding a provider does not require rebuilding the customer application or banking database.
- Card model
- Authorization
- Settlement
Provider-neutral card architecture
The platform keeps the customer card experience and banking data model separate from a specific processor implementation.
This architecture supports physical and virtual cards across debit, prepaid, consumer, business and premium or HNW program models, depending on issuer and processor configuration.
Card lifecycle and state management
- Issue and activate
- Freeze and unfreeze
- Block and reissue
- PIN management
- Sensitive card details
- Limits and card states
- Customer notifications
Authorization, accounting and settlement
Authorization decisions can use real-time balances and configured risk rules while persistence, ledger posting and customer notifications follow through the same platform.
Authorization, settlement, refunds, reversals and reconciliation connect directly to the bank ledger.
Wallets and authentication
Bastion supports 3DS through partners and digital-wallet integration options.
Apple Pay support depends on the selected issuer, processor, program configuration and required certification readiness.
Processor and wallet availability is deployment-specific; historical integrations are not presented as universally active.
Related capabilities
Keep the financial model connected
See the module in context
See how this capability works inside the complete Bastion platform.
We can demonstrate the running product and discuss how the module could fit your existing infrastructure.
[email protected]