Open Banking recalls: instant deposits are not the same as instant withdrawals

A recall in Open Banking is what happens when a customer reverses a bank transfer before it reaches final settlement. For merchants in high-risk verticals, the operational problem is simple: you can see an initiated payment and credit the balance, but the money may still be reversible at the bank level.

1. There are two different payment states. The source text breaks the transfer into Partial/Initiated and Final/Settled. In the first state, the payment looks successful to the system. In the second, the funds have actually landed in the recipient’s account.
2. The gap exists because not all EU banks support SEPA Instant. If the sender’s bank uses ordinary SEPA, the transfer can take hours or even days, especially over weekends. That window between “sent” and “settled” is where the abuse happens.
3. The abuse pattern is straightforward. A customer makes a deposit, the platform sees Initiated and credits the account immediately, the customer places a minimal amount of activity — sometimes just a couple of bets — then requests a withdrawal and recalls the outgoing payment in their own bank. The merchant ends up paying out before the deposit ever settles.
4. The merchant’s choice is speed versus exposure. On paper, the clean compromise is to credit the deposit on the first status to preserve the instant-deposit experience, but block withdrawals until the bank confirms Settled. The article also flags a behavioral pattern worth watching: deposit, minimal activity, then an immediate withdrawal request. That is a control signal, not a coincidence.
5. The practical takeaway is blunt. Fast balances are fine. Fast payouts should wait for final status. Until more banks move to Instant SEPA, the gap between Initiated and Settled will keep existing, and the real question for PSPs is who manages it without leaking money.