Troubleshooting
“Transaction failed with Oracle Signature Invalid”
Cause: Oracle signer mismatch, signature deadline expired, or network mismatch (e.g. signed for mainnet, sent on testnet).
Fix: Wait 30 seconds and retry. The Oracle re-generates a fresh signature on each attempt. If it persists for more than a few minutes, the Oracle may be temporarily offline — try again later.
“Swap failed”
Cause: Insufficient liquidity in the Uniswap pool, slippage exceeded, or wrong SwapRouter address.
Fix:Try a smaller amount, or wait for better liquidity. Check that you're on the right network.
Funds Are Safe
“Transaction stuck on pending”
Cause: Low gas price, network congestion, or RPC node issue.
Fix:Check the transaction on BaseScan. If it's been pending for more than 10 minutes, try speeding it up in MetaMask (click on the pending tx → Speed Up). On Base L2, transactions normally confirm in under 3 seconds — a stuck tx usually means an RPC problem.
“Webhook not received”
Cause:Your endpoint returned a non-2xx status, timed out (>10s), or the HMAC signature verification failed.
Fix: Check the webhook delivery logs in the Command Center (Settings → Webhooks → Logs). RSends retries with exponential backoff:
| Attempt | Delay |
|---|---|
| 1st retry | 30 seconds |
| 2nd retry | 2 minutes |
| 3rd retry | 8 minutes |
| 4th retry | 32 minutes |
| 5th retry (final) | 2 hours |
After 5 failed attempts, the webhook is marked as failed. You can manually resend it from the dashboard.
“Payment intent expired”
Cause:The payer didn't complete the payment within the expiry window (default: 30 minutes).
Fix: Create a new payment intent. Expired intents cannot be reactivated. If the payer sent funds after expiry, the payment is recorded as a generic transfer — it still goes through, but the intent is not fulfilled.
“Balance shows $0 on Tron/Solana”
This is expected. Portfolio data for non-EVM chains is being integrated. Your funds are there — use TronScan or Solscan to view your full balance until dashboard support is live.