Implemention Guide
This page walks through the five usual ways to use Rocketfuel Payouts.
Full collection: Rocketfuel Payouts (Postman)
Scenario 1 — Onboard a payee
Add the person you want to pay, verify their identity, then move money from your payout account onto their balance.
1. Invite the payee
Postman: Payee Invite
Send their name, country, email, and your own reference id (for example VENDOR-1001).
You get back a payee id. Save it.
If you see “Payee already registered”, look them up with Payee List instead of inviting again.
2. Submit KYC
Postman: Payee KYC
Use the payee id from step 1. For a person, send name, country, date of birth, and address. For a company, use the company option in the same Postman request.
KYC can take a little time. When it is completed, they can receive money. You can also check status with Payee Detail.
3. Put money on their balance
This is two steps: start the allocation, then confirm it. Make sure your merchant account has enough funds first (see Scenario 4).
Start — Initiate Allocation
Send the payee id, amount, currency (usually USD), and a short note such as “March payout”. Save the allocation id.
Confirm — Confirm Allocation
Use the allocation id and payee id. After this, the money is on the payee’s balance.
Changed your mind before confirming? Cancel it in Scenario 5.
4. Check their balance
Postman: Payee Balance
You should see the amount you just allocated. They are now ready for a bank or crypto payout.
Also useful: Payee List · Payee Detail · List Allocation
Scenario 2 — Pay to a bank and check status
Send money from the payee’s balance to their bank account, then check whether it arrived.
Finish Scenario 1 first. In Postman, put the payee id on every request in this flow.
1. Make sure bank payouts are available
Postman: Fiat Transfer Availability Check
If fiat is not enabled, email [email protected].
2. Create their payout profile
Postman: Create payout account
Send first name, last name, email, and country (three-letter code such as USA).
3. Pick country, currency, and method
Open these in order and keep what Postman returns:
Payment options (wire, instant, next day, and similar)
4. Save their bank details
Load the form first — fields change by country.
You get back an account token. That is the bank account you will pay into.
Later: List Bank Details · Delete Bank Details
5. Check the fee, then send
Fee — Pre-Validate Fiat Transfer
This shows how much they will receive and gives you a record id. If you see an allocation error, they do not have money on their balance yet — go back to Scenario 1.
Send — Fiat Transfer
Use the account token, amount, currency, and record id. You get back an order id. Status starts as pending.
6. Check if it went through
Postman: Transfer Status
Use the order id and payee id.
Pending (
0) — still processing; wait and check againSuccess (
1) — money sentFailed (
-1) — it did not go through; check the message or contact support
Scenario 3 — Pay to crypto and check status
Send money from the payee’s balance to a crypto wallet, then check whether it arrived.
Finish Scenario 1 first. In Postman, put the payee id on the currency, fee, and transfer requests.
1. See which coins you can pay in
Postman: Payout Currencies
Pick a currency and network (for example USDC on Ethereum). Use those same names in the next steps.
2. Check the wallet address
Postman: Know your address
You want approved. If it is not approved, do not send the payout.
3. Check the fee, then double-check
Crypto Transfer Fee — what the transfer will cost
Pre-Validate Crypto Transfer — confirms amount, wallet, and network
If you see “Payee is not eligible”, KYC is not finished or the payee is blocked.
4. Send the transfer
Postman: Crypto Transfer
Send the amount, coin, network, and wallet address. If the wallet is not the payee’s own, fill in the owner’s name in the Postman request.
You get back an order id. Status starts as pending.
5. Check if it went through
Postman: Transfer Status
Same as bank payouts: pending 0, success 1, failed -1. When it succeeds, you may also get a blockchain transaction hash.
Scenario 4 — Check your balance
See how much you can pay out, and add more money if needed.
Do this before you allocate if you are not sure there is enough in the account.
1. Check how much you can allocate
Postman: Check Balance
Available balance — money you can still put on payees
Current balance — money sitting in your payout account
Allocated funds — money already given to payees
2. Check the live balance
Postman: Check Running Balance
This includes allocations still in progress, so it can differ from available balance for a short time.
3. Add funds
Ask Rocketfuel for your wiring instructions (the bank account you send money to). After the wire arrives, Check Balance should show a higher available amount. Then go back to Scenario 1 and allocate.
Note: You fund your merchant payout account once, then split that money across payees. You do not wire money to each payee directly.
4. Check one payee’s balance
Postman: Payee Balance
Use this after an allocation to confirm they received the funds.
Scenario 5 — Take money back or pause a payee
Use this if you allocated too much, a job was cancelled, or you need to stop paying someone.
Note: You can only take back money that is still on the payee’s Rocketfuel balance. Once it has been sent to a bank or a crypto wallet, these steps will not reverse it. Blocking does not take their money back. Reclaim first if you also need the unused balance.
Cancel a pending allocation
If you have not confirmed the allocation yet:
Postman: Cancel Allocation
Use the allocation id and payee id. To find pending ones: List Allocation
Take unused money back
See how much you can take — Reclaim balance
Take it back — Reclaim Funds
Send the payee id, the amount (not more than the reclaimable balance), and a short reason.
Then check Payee Balance (should be lower) and Check Balance (your account should be higher).
Pause or restore a payee
Block — Payee Block — they cannot receive more payouts
See who is blocked — List Blocked Payee
Unblock — Payee Unblock — they can be paid again
Last updated
Was this helpful?