Here's what our card issuing has been up to in Q1: Three updates shipped to the CaaS platform in March — across cardholder identity verification, card inventory visibility, and AML transaction monitoring. All three are live. If any of these touch areas you've been working around, it's worth a conversation with your account team.
1. Universal KYC: Submit Verified Cardholder Identity Data Directly to Reap
Until now, every CaaS client onboarding cardholders had one path: route identity verification through Reap's KYC infrastructure. For programmes built from the ground up on our stack, that works well. But for clients who already operate their own compliance infrastructure, running identity checks through Jumio, Onfido, or another provider, often across multiple markets, being required to run cardholders through a parallel Reap verification flow created duplication that wasn't justified by the compliance outcome.
The problem isn't unique to any one client. As card programmes scale and operate across more jurisdictions, KYC infrastructure tends to become embedded, tied to existing onboarding flows, internal data handling policies, and in some cases, regulatory agreements about which entity controls the verification process. Forcing a second verification layer in that context adds integration overhead and, in some cases, creates questions about where cardholder data sits and who controls it.
What's changed
Universal KYC (UKYC) is now available to eligible CaaS clients. Rather than routing cardholders through Reap's verification flow, your system submits a standardised identity payload directly to Reap via API, including identity details, document data, proof of address, and liveness check result — using data already verified through your own KYC provider. Reap validates the submitted data against our policies and issues card creation approval from there. Your KYC provider and your verification process stay in place. Reap retains final approval authority on card issuance.
What this means for your programme
For eligible clients, UKYC removes the need for additional parallel verification layer, allowing faster card onboarding.
Who this affects
UKYC is only available for programmes that qualify for Reap's Reliance model. Specifically, clients who operate their own KYC framework under a regulatory licence and have an established AML policy in place. KYCaaS remains the default for all other clients.
If you're unsure whether your programme qualifies, your account team is the right starting point. They can walk you through the eligibility criteria and what onboarding looks like if you do.
What to do
Contact your account team to discuss eligibility. If your programme qualifies, your account team will connect you with the implementation team to begin onboarding.
→ Here’s how to implement UKYC: UKYC integration guide
2. Card Inventory Data Now Available in GET /card-design
If you're issuing physical cards at volume, stock visibility matters. Knowing when a particular card design is running low — before you hit a stock-out — is the difference between a planned restock and an emergency. Until now, getting that information meant contacting Reap. Your team would ask, we'd check, and you'd get a number back. That process works at low volume, but it doesn't scale, and it creates a dependency on Reap for information that should just be queryable.
What's changed
The GET /card-design endpoint now returns live inventory data alongside existing design details. For each card design on your account, the response includes an inventories array showing openingStock, closingStock, and a last-updated timestamp. This is a non-breaking, additive change — your existing integration continues working as-is, and the new fields are there when you're ready to use them.
What this means
Your team can now query card stock levels directly, per design, without contacting Reap. That means you can build inventory visibility into your own operations workflows — monitoring thresholds, triggering restock requests, or surfacing stock status in internal dashboards — on your own schedule.
Who this affects
Any client issuing physical cards. If you only issue virtual cards, this update does not apply to your integration.
What's coming next
Dashboard support for card inventory is in progress and will be announced separately. The physical card restock request flow — which lets clients submit restocks directly without contacting Reap — is already live and covered in the April edition.
What to do
No integration changes are required to keep existing functionality working. If you want to start using the inventory data, update your integration to read the new inventories field from the GET /card-design response. Documentation is below.
→ GET /card-design API reference
3. Card Transaction Monitoring Is Now Live
Real-time AML transaction monitoring for card activity across Reap's platform is now live in production. All card transactions processed through Reap's HK BINs - across CaaS, Direct, and BIN Sponsorship - are now flowing into a live monitoring system and being screened against an active AML rulebook in real time.
What's live
Sixteen AML rules are configured in production and actively screening every transaction. The system operates at the individual cardholder level; transactions are linked to specific cards and cardholders, not just to a business account, which means compliance review and case management can be done at the right level of granularity. Historical transaction data covering December 2025 through March 2026 has been backfilled, so there are no gaps in the monitoring record from the point of integration onwards.
The rules are currently running in shadow mode — screening transactions and generating alerts, but with enforcement thresholds being calibrated against real transaction patterns before full activation. This is standard practice for AML system launches and allows our compliance team to validate alert quality before rules move to enforcement.
This does not affect card authorisations or any client-facing behaviour.
What this means for your programme
There is nothing for your team to action. This monitoring runs entirely within Reap's infrastructure and has no effect on card authorisations or cardholder-facing behaviour during the calibration period.
We're sharing this because it's relevant context for your own compliance and audit conversations. Reap operating systematic, real-time AML transaction monitoring on the card programme is a meaningful part of the compliance posture of the platform.
Who this affects
All CaaS and Direct clients.
What to do
No action required. If you'd like more detail on how the monitoring works or what it covers, reach out to your account team.
