News / Crypto

Crypto Debit Cards Leave Brands Exposed to Upstream Failures

Original Presence illustration of connected digital asset networks.
Illustration: Presence

Some wallet and fintech brands possess minimal control over their payment services, a vulnerability highlighted by a $1.1 million exploit of a Rain contract that demonstrated the dangers inherent in shared infrastructure. This incident involved shared banks, processors, and middleware which can expose separate card brands to identical failures, while the August attack specifically targeted funded card balances without compromising customers' personal wallets or private keys.

Ron Tarter, who serves as co-founder and CEO of MNEE App, told the report that firms depending too much on banking-as-a-service platforms might only manage their app interface, card design, and marketing efforts. He advises forming direct bank ties and keeping customer data accessible without relying on third parties to reduce these dangers. According to Tarter, while US deposit insurance safeguards eligible funds held at banks from institutional failure, it offers no shield if a fintech provider goes under.

Shared Infrastructure Risks

Ron Tarter, co-founder and CEO of MNEE App, explained that the operational architecture of crypto debit cards typically involves a sponsor bank managing banking permissions and holding fiat deposits while a processor handles transaction authorization. He noted that functions such as identity checks, compliance monitoring, fraud prevention, and crypto wallet services may be provided by separate vendors rather than the brand itself. Tarter emphasized that even with millions of users and a strong brand reputation, a company might not possess final authority over its own product if these critical components are outsourced.

In Tarter's account, founders frequently underestimate the extent of a sponsor bank's authority, which allows the bank or program manager to restrict or terminate a program deemed too risky. This action can leave the consumer-facing company unable to restore service independently. As an example of this vulnerability, he cited Kulipa's summer insolvency, which he stated disrupted card programs serving roughly twenty wallets and fintechs. He added that customers may only discover such an interruption when attempting to make a payment.

Distinct events resulted in financial damage within the payment infrastructure. Gnosis stated that an assault on June 1 took advantage of software components powering its card-safe system, which brought card services to a halt. A postmortem released on July 3 indicated that intruders removed $1.5 million and made another $300,000 unavailable. The firm covered these costs and returned the money to users.

According to Blockaid's analysis of the Rain card exploit, a legacy contract on Aug. 28 put multiple Solana-based card initiatives at risk of losing about $1.1 million. The intruder focused on stablecoin collateral held for transactions, avoiding access to individual wallets or private keys.

Tarter advises determining the location of customer funds prior to choosing a partner, specifying whether they reside in individual bank accounts or a pooled arrangement often termed an FBO account. Regarding pooled resources, he notes that firms must inquire about ledger reconciliation responsibilities, frequency, and if the financial institution maintains its own records. His ideal protections involve accounts bearing customers' names alongside daily balance and record copies retained by the brand.

Regulatory conditions govern US insurance coverage differently. The Consumer Financial Protection Bureau's examination of payment applications indicates that pass-through deposit insurance is contingent upon meeting specific regulatory mandates. Such insurance shields against failures of the insured bank but offers no protection if the nonbank application provider fails.

To ensure security, the executive suggests obtaining independent evaluations like SOC 2 Type II reports and inquiring how a platform oversees other initiatives utilizing its infrastructure. When discussing insurance, it is essential to define the scope of covered losses and determine if a significant event would cause financial strain on the provider.

Tarter cautioned that selecting two providers does not automatically guarantee independent backup systems. Both entities might depend on the same sponsor bank, which leaves the brand vulnerable to choices made by a single institution.

Tarter cautioned that enlisting two vendors does not guarantee truly separate backup systems, as both could rely on a single sponsor bank, thereby exposing the brand to the decisions of one entity. He noted that clearing a single bank's underwriting requirements took over a year; although multiple issuers and backup processors can assist during brief interruptions, every new partnership introduces additional technical integrations, compliance steps, and ledgers requiring reconciliation. Larger financial technology firms can manage these setups more readily, whereas smaller enterprises may find the associated expenses and labor burdensome.

Regulatory and Insurance Gaps

The executive advises mapping all intermediaries, securing a list of subcontractors, and determining if direct communication with the sponsor bank is feasible. Agreements must cover scenarios involving an upstream provider's acquisition, closure, security incident, or choice to stop services. A distinct data breach in November at Gnosis Pay impacted its branded consumer cards, though the firm stated its enterprise platform and customer funds remained safe.

Tarter advises securing direct contractual rights to maintain or transfer a program, along with advance notice before termination, in preparation for a provider's collapse. He pointed out that MNEE had previously scrapped plans to launch FBO accounts via an unnamed vendor due to worries over the absence of a direct bank link; that vendor later ceased operations and filed for Chapter 11 bankruptcy.

About the author

Presence Editorial is the editorial team behind Presence.