Standard errors
Tribridge uses standard HTTP response codes. The most common ones:
Payment-level failures (not HTTP errors)
These arrive as webhook events, not error codes — your handler must expect them:
- Underpaid / overpaid — the customer sent the wrong amount. Tribridge emits
payment.underpaid / payment.overpaid and refunds automatically (see Refunds). Never assume received equals invoiced; never fulfill on a mismatch.
- Expired —
payment.expired means nothing arrived before expires_at. Release held stock and let the customer start a fresh payment.
- Signature mismatch — your webhook verification rejected a payload. Return non-2xx so Tribridge retries; then check you’re hashing the raw body with the correct endpoint secret.
Fulfillment rule of thumb: fulfill orders only on verified payment.completed events. Redirects can be faked and payment.confirmed precedes the final sweep — completed is the terminal success state your business logic should key on.
