Skip to main content
Use webhooks first. Call monitor-status when the user refreshes or a callback is delayed.
When to use thisThis is your recovery path, not your primary state source. Use it when you need to confirm what happened after the webhook path slowed down.

Request

POST /api/developer/orders/:transactionId/monitor-status The recovery response includes the latest RampHub truth for the transaction. The most useful fields are:
boolean
string
string
boolean
boolean
string
boolean
boolean
boolean
For test-key flows.
object | null
Present when PayChain has extra settlement context.

Recovery rules

  1. Listen for RampHub webhook events first.
  2. Update local order state from webhook payloads.
  3. Call monitor-status only when the user refreshes or a callback is delayed.
  4. Mark an order terminal only when RampHub reports completed or failed.
  5. Do not guess provider instructions or settlement state.
  6. If a webhook stops verifying after a secret rotation, update the receiver secret first, then use status sync to recover the current truth.