Stripe's crypto checkout generates a one-time deposit address that is only valid while the checkout session is open. If your exchange processes the withdrawal slowly and the transfer lands after the session times out, the confirmation webhook that would credit your account never fires — and an automated transfer out of that address a minute or two later is typically the processor's own system sweeping the late funds into its main wallet. That sweep looks alarming on the explorer, but in the typical case it is not theft — the funds are sitting unreconciled at the payment processor, which is exactly what their support has to confirm.
Because the session is dead, there is no self-serve path — a human has to match your on-chain transfer to your account. Open a ticket with the service's support and say precisely this: the funds arrived at the session's deposit address after expiry and were swept by the processor, so you need a manual reconciliation (credit or refund) through their Stripe integration. Attach the transaction hash, the deposit address, the amount and token, the session or checkout URL, your account email, and the UTC time of the transfer. That evidence set is what lets their billing team locate the sweep — without the hash, a generic first reply is all you will get.
Do not pay again until the first payment's fate is decided, and do not send anything more to that deposit address — one-time addresses are never reused. To avoid a repeat: time-boxed crypto checkouts and slow exchange withdrawals are a bad combination, so pay them from a wallet you control, and keep exchange withdrawals for deposit addresses without a short expiry window. ROZO is independent and not affiliated with OpenRouter, Stripe, or Coinbase.