RAMBOCARD BLUE CARD EDUCATION · Updated 2026-07-30
Understand preauthorization, small verification holds, merchant refunds, reversals, settlement and posting timing.
A preauthorization is not always final spending, and a refund is not instant balance. Users need to read card activity as authorization, settlement, reversal and refund events.
A merchant may temporarily hold a small amount to verify that the card can be used. The hold may be reversed or later settled as a final charge. If the page only shows one balance number, users can easily mistake this for duplicate billing.
A refund requires merchant initiation, upstream receipt, issuer processing, platform reconciliation and ledger posting. Timing varies by merchant and issuing program; a static article cannot promise a fixed number of days.
Support should locate the original authorization or settlement first, then check for reversal, refund or dispute events. Before upstream return, projected refund should not be treated as available balance or promised as an advance credit.
If a card is frozen by bank risk controls or closed, the card balance cannot be operated, withdrawn or returned to platform USD balance. Because upstream providers cannot release it either, the balance is permanently locked at the issuing bank.
Use event language instead. It may be reversed, settled or refunded by the merchant, and the final state depends on issuer-side events.
Wait for upstream return and reconciliation. A merchant email or screenshot does not replace issuer-side posting.
After bank risk freeze or card closure, card balance cannot be returned to platform wallet.
Sign in to review live card programs, fees, funding options, card status and issuing API access. Static articles are educational; production operations follow the signed-in workspace.
Sign inInsights hub