Platform capability
Virtual card operations
RebateCardX card records store only provider references and masked metadata. API and queue controls reject raw PAN, CVV and PIN, while permitted private documents are encrypted before object storage.
Route recovery
Return an unmatched request to a known Rebate Cards path.
The requested route is outside the current website map, so navigation returns to published program information.
- 01 / Request
Unknown pathname
A browser asks for a route that is not present in the current site map.
- 02 / Router
Path resolution
- Normalise the request
- Compare published routes
- Preserve a clear 404 response
- 03A / Option
Return home
Restart with the main Rebate Cards business-model overview.
- 03B / Option
Explore industry models
Continue to rebate models, economics, insights or contact.
- 04 / Website
Published navigation
Only current, intentional destinations are presented as available pages.
- 05 / Recovery
A valid next request
The visitor selects a known destination and resumes the information journey.
What it covers
Operational capability with a controlled state model.
- 01Lithic account-holder and card lifecycle
- 02Online, merchant and category controls
- 03Pause, resume and close operations
- 04Masked card views and provider-managed 3DS when approved for the Lithic program
Operational outcome
Card operations remain useful to merchants and recipients without expanding the platform data boundary into raw cardholder data.
Rebate program strategy
Apply this capability to a funded merchant campaign.
Define who funds the rebate, what qualifies, how value is calculated and how program performance is measured.
Start building