Your prop firm payout is approved. What happens before you can spend it?
Payout approval, payment dispatch, blockchain confirmation and receiving-account availability describe different events. A provider may combine or name them differently, so check its own status information. To locate a delay, identify the last confirmed event and the provider responsible for the next one rather than assuming that approved means ready to spend.
By BullSwipe
You receive an approval email, but the balance you want to use has not changed. The useful next question is which part of the journey has actually finished. A status from one service may describe only its own part of the payment.
Approval belongs to the payout provider
Read what the firm's approval message says. It may confirm an internal decision without establishing that a transaction has been sent. Use the firm's current instructions to understand its terminology and processing period.
If you have approval but no evidence of dispatch, contact the payout provider. A receiving app cannot locate an on-chain payment solely from an internal approval reference.
Dispatch needs its own evidence
For an on-chain payout, the provider may supply a transaction reference after sending it. Check the network as well as the reference. A payout processor's internal reference is not necessarily a blockchain transaction hash.
If the reference is unclear, ask the sender what it identifies. Do not treat a screenshot of a request as proof that the network has processed a transfer.
A network record describes the transfer
A blockchain explorer for the correct network can help you inspect an on-chain transaction. A hash identifies the transaction; the record may show its status and transfer details. Use the network's own documentation to interpret what you see.
That record cannot tell you whether a separate service has completed its account review or made a balance available for spending. A successful network transfer and an available app balance answer different questions.
The receiving service controls account crediting
Check the receiving service for its own deposit status. It may require network confirmations or other checks. For BullSwipe deposits, the current guide explains pending transfers and the information to provide when asking for help.
If the network record and the receiving balance differ, gather the asset, network and transaction reference. Contact the receiving service through its official support channel. Do not repeat the transfer just to see whether a second one arrives sooner.
Spending may involve another step
Receiving stablecoins in one wallet does not automatically create a spendable balance in another service. Any later transfer or conversion has its own requirements.
BullSwipe's spending explanation describes supported stablecoin conversion to a USD balance for its virtual card. Before using that route for a prop firm payout, confirm the permitted funding source, account eligibility and receiving instructions. Do not infer direct payout compatibility from token support.
Send the question to the right place
| Last confirmed event | Useful next question |
|---|---|
| Request accepted or approved | Has the payout provider actually dispatched the payment? |
| Sender reports dispatch | Which network and transaction reference identify the transfer? |
| Network transfer confirmed | What does the receiving service show for this deposit? |
| Receiving account credited | What steps and requirements apply to the spending method? |
This is a way to investigate the process, not a fixed timetable. Keep the records private and use verified support channels. The goal is to identify the unresolved step without promising a completion time that no source has established.