Built for card programmes that need precise control and security

Thredd provides the flexibility and oversight needed to manage card settings, usage and security.

Configure physical and virtual card characteristics
Set structured usage and spend controls
Adjust settings after issuance as programme needs change
Keep card behaviour secure and consistent across channels

Control across your card programme Control across your card programme

Flexible card configuration

Configure physical and virtual cards, customise appearance, and define key characteristics including status, PIN and expiry.
Structured usage and spend governance

Define usage groups, velocity limits, MCC controls, FX settings and permission rules to govern how and where cards can be used.
Dynamic settings management

Change card controls, fee groups and selected settings after issuance via web services, without reissuing cards.
Configurable fee structures

Set authorisation, recurring and web service fees within defined fee groups to fit your programme's commercial model.
Built-in security controls

Enable EMV Chip and PIN, AVS, CVV2, tokenisation and 3D Secure across online, in-store and mobile channels.

The Thredd difference

Card settings update via your existing integration, so programme changes don't require re-integration or manual reissuance, reducing operational overhead as you scale.
Structured usage controls and built-in security mean fraud exposure is contained without adding operational complexity to your team.
Fee groups configured to your programme model, so your commercial structure is built in from the start, not retrofitted later.
Consistent control across physical and virtual cards means you manage both card types within a single environment, without duplicating processes or tooling.
Settings adjustable after issuance, so your card programme can evolve without the cost or disruption of reissuing cards.

Across different card programmes

Controlled spend programmes

Define usage groups, velocity limits and merchant category controls to govern how and where cards are used, with rules that stay adjustable as programme requirements change.

Virtual and digital-first cards

Configure virtual cards with usage restrictions, tokenisation and 3D Secure built in. Update settings as needed to keep pace with online and mobile environments.

Feature-rich card products

Set card characteristics, fee groups and security settings across physical and virtual cards, and refine them after issuance without reissuing cards or reworking your integration.

Frequently asked questions

Card control groups, fee groups and many other settings can be changed using Thredd's web services without reissuing cards. Some settings may require configuration by your Thredd Implementation Manager or Support team.
Yes. Virtual cards can be configured with defined usage restrictions, while physical cards can support in-store, online and ATM usage depending on programme design.
Yes. If you provide a customer portal or app, your customers can update card settings. Your backend systems use the Thredd web services API to apply those changes.
Card programmes can include EMV Chip and PIN, AVS, CVV2, tokenisation and 3D Secure, depending on your configuration and scheme requirements.
Fee groups can be configured to fit different programme models, including authorisation, recurring and web service fees.
Thredd provides a test environment for trying out the REST API prior to integration. Your implementation manager can coordinate test card production with your card manufacturer.