A player can fund their wallet directly from a bank account. This is a pull: bank account → wallet. It is same-account — a pull funds the player's own wallet from the player's own bank. The credit settles asynchronously once the bank clears the debit.
This guide walks a casino-style platform through the full money lifecycle on Pathly: onboarding players, taking deposits, paying out winnings, and letting players cash out to their own bank account.
Cashing out moves a player's wallet balance to their own bank account. This is a push: wallet → bank account. It is same-account — you can only cash out a wallet to that same account's bank. It settles asynchronously over the bank rail.
Bank-rail transfers (funding pulls and cash-out pushes) settle asynchronously, so subscribe to webhooks instead of polling. Add a webhook from your Developer Dashboard and subscribe it to the events you care about; you'll get the Signing secret used to verify each delivery.
Alongside the USD wallet, an account can hold a crypto wallet — a USDC balance on-chain (currently BASE-USDC, USDC on the Base network). Loading it works like a bank pull, but the rail is on-chain: get the deposit address, have the player send USDC to it, then watch for the credit.
POST /transfers is the same single endpoint used for fiat transfers — you get crypto behavior by setting currency to a crypto code (e.g. BASE-USDC) instead of USD. Two shapes are supported:
Crediting a player — winnings, a deposit you collected by card, a bonus — is a wallet → wallet transfer from your merchant wallet to the player's wallet. It is internal: instant and final (born posted), no bank rail involved.