Help Center
Understanding payment statuses
Status names and transitions vary by API and rail. Read the response for the specific route; a prepared request, payment ID or accepted HTTP response is not proof that funds settled.
Common status meanings
| Parameter | Type | Description |
|---|---|---|
| preparedoptional | not submitted | The route built an intent or transaction data. No chain transaction is implied. |
| pendingoptional | in progress | A request was submitted or accepted and is awaiting a later confirmation or review. |
| pending_reviewoptional | manual review | A policy requires a human decision before a payment can proceed. |
| settledoptional | confirmed | The route reports successful settlement. Verify the transaction reference on the stated network. |
| failedoptional | unsuccessful | The route did not report successful settlement. Inspect the error and check the chain before retrying. |
| rejectedoptional | not accepted | Validation, policy, availability or authorization checks refused the request. |
A 202 Accepted response means processing is pending; it is not a settlement receipt. A 503 or missing status means the service cannot confirm availability.
Verify an on-chain transaction
When the API returns a transaction hash, check it on the explorer for the exact network in the response. Compare the sender, recipient, token and amount. Wait for the chain's required confirmations before treating the transfer as complete.
Before retrying
Do not submit a second payment while the first one is pending or its status is unknown. Check the original payment ID and transaction hash first. Use the documented idempotency behavior for that route, and contact FurlPay Support if the API status and chain evidence disagree.
Availability is separate from status
/api/rails before creating a payment, and never interpret a quote or challenge as a completed transfer.