Status definitions
| Status | Description | Client action required? |
|---|---|---|
pendingFunding | Pythas is waiting to receive funds from the client. Applies to incoming wire, ACH, or stablecoin deposits. | Yes — send funds |
pendingReview | Transfer data needs further confirmation. Typically resolves within hours. Pythas will contact the client within 24 hours if not resolved. | Standby |
fundsReceived | Pythas has received the funds and is preparing to process the transfer. | No |
processing | Conversion and settlement in progress via OTC Liquidity Provider and banking partners. | No |
succeeded | Transfer complete. Funds delivered to destination wallet or bank account. | No |
returned | Transfer was returned by the destination bank. Funds will be returned to the client. | Contact Pythas |
failed | Transfer failed. Funds will be returned to the client as a refund. | Contact Pythas |
pendingRefundInfo | Pythas needs additional information to process the refund. | Yes — provide details |
refunded | Funds successfully returned to the client originating account. | No |
failedPrecondition | Transfer failed because the client provided invalid information. | Contact Pythas |
Status lifecycle
Return and refund policy
When a transfer cannot be completed, Pythas initiates a return to the originating account.| Scenario | Return timeline | Notes |
|---|---|---|
| Bank-rejected wire (wrong account number) | 3-5 business days | Correspondent bank processing time applies |
| Compliance hold — resolved | Same day as release | Client notified by compliance team |
| Compliance hold — unresolved | Up to 30 business days | Subject to regulatory review obligations |
| Failed on-chain delivery (wrong address) | Case by case | On-chain errors may be irreversible |
| ACH return | 2-5 business days | Standard ACH return window per NACHA rules |
| PIX / SPEI / SEPA return | 1-3 business days | Via Local Rail Partner — timeline varies by corridor |