Reap Launches Virtual Asset Ledger for Bitcoin-Funded Card Spending
Clients retain custody of underlying assets while Reap authorizes card transactions against mirrored balances and settles network debt from USDC or USDT collateral.
Reap launched its Virtual Asset Ledger on September 9, giving clients of its card-issuing platform a way to make bitcoin balances spendable through their card programmes. The company says bitcoin support is available now through its existing API.
The product does not transfer a user's bitcoin into Reap for each card purchase. A client keeps custody of the underlying asset, mirrors a spendable unit balance into Reap and supplies the price used to value it. Reap authorizes card transactions against that ledger balance and settles card-network debt from a master collateral account maintained in USDC or USDT. Reap.
The card spends against a mirrored balance
Reap's API documentation describes a virtual asset as a unit balance that the platform tracks on a client's behalf. The client defines the symbol, display name and exchange-rate source, then allocates units to an individual account. Those units contribute to the user's available card balance.
The underlying asset remains on the client's own side of the arrangement. Reap's documentation says real crypto is not moved when a virtual-asset allocation is created. A wallet or exchange can therefore mirror a bitcoin balance into the card programme while continuing to control custody and the customer relationship.
That architecture separates three things that are often compressed into the phrase “spend bitcoin”: the asset held by the client, the ledger units used to calculate card spending power, and the collateral used to settle what the card programme owes. Reap API documentation.
Stablecoin collateral funds the card obligation
For a programme-funded deployment using Reap's managed authorization mode, the client maintains a master collateral account. Reap says it uses that account to authorize, clear and settle card transactions with the card network.
When a user pays, Reap values the active ledger allocations in the programme's billing currency and subtracts outstanding card debt. The client later posts a settlement entry that reduces the user's virtual balance and clears the corresponding liability.
The commercial consequence is a simpler integration for platforms that already custody assets. They do not need to send every user's bitcoin to a card issuer or build a separate authorization and settlement stack. They still carry the work of custody, pricing, reconciliation and keeping the collateral account sufficiently funded.
Reap's release says conversion takes place at the platform's live rate at the point of sale. The client selects the rate source and remains responsible for treasury management and conversion. The announcement does not disclose the spread, fees, rate-update interval or safeguards applied when a volatile asset moves between authorization and settlement.
Bitcoin support is live for issuing clients
Reap says bitcoin support is available now to clients of its card-issuing platform through the existing API. Its release describes cards issued from Hong Kong and Mexico that can be used wherever Visa is accepted. That statement concerns card acceptance after issuance; it does not establish that every business or consumer worldwide can enroll in one of those programmes.
The ledger can also represent fixed-rate programme units such as cashback, loyalty points, salary allowances and credit lines. Reap's documentation gives examples involving USDC, USDT, ether and bitcoin, but those examples should not be read as a list of assets automatically available in every client programme. The client defines the balances it offers and the associated rate source.
This launch is separate from Reap's agentic-payments material. The Virtual Asset Ledger documentation is live, while the documentation navigation inspected on September 14 still labels the agentic-payments section “Coming Soon.”
Custody stays separate from settlement control
The Virtual Asset Ledger lets a card programme expose one available balance across assets and programme credits without putting each underlying asset into the card issuer's custody. That can reduce product fragmentation for a wallet, exchange or neobank whose users already hold bitcoin alongside cash or rewards.
It also makes the operating boundary clearer. Reap controls card authorization, clearing and settlement against the programme collateral. The client controls the underlying assets, prices, customer ledger synchronization and treasury conversions. A merchant receives a conventional card payment; the launch does not make bitcoin a new merchant-acceptance rail.
The next evidence should come from production programmes: named clients, actual supported assets, pricing, settlement timing, loss allocation and performance during volatile markets. Until those terms are disclosed, the verified change is infrastructure availability for Reap's issuing clients, not a universal bitcoin card product for consumers.