Event Types
| Event | Fired when |
|---|---|
payment.created | A payment has been created in Tesser's system |
payment.quote_created | Route planning is complete; execution steps are created with exchange rate info |
payment.balance_updated | Balance check result is available (reserved or awaiting_funds) |
payment.risk_updated | Risk status has changed (e.g. auto_approved, awaiting_decision, or auto_rejected) |
payment.updated | General notification that a field on the payment has been updated. |
payment.expired | The payment reached its expiration date-time and is no longer actively processing |
For a detailed breakdown of what each event means in the context of a payout, see Payment Workflow.
Step Events
Once steps are created (payment.quote_created), individual step lifecycle events fire as each step progresses:
| Event | Fired when |
|---|---|
step.signature_requested | Signature has been requested for the step |
step.signed | Step has been cryptographically signed |
step.submitted | Step has been submitted for execution |
step.confirmed | Step execution is confirmed on-chain or by the partner |
step.completed | Step finished successfully |
step.failed | Step encountered an error and could not complete |
step.updated | General notification that a field on the step has been updated |
The data.object for Payment step events is a PaymentStep resource.
Payload
The data.object for each top-level Payment event contains the full payment resource, including its steps. See General for the envelope shape and an example payload, and the Payment schema for the full field reference.
Key Status Fields
For details on how risk_status and balance_status evolve through a payout, see Payout Workflow.
Last modified on