Skip to main content
The Telr admin surface currently exposes a single operator endpoint: manual reconciliation. Telr’s hosted-checkout sandbox occasionally drops the txnref webhook, leaving an order in PENDING even after the customer completes payment. Reconcile pulls the canonical state from Telr and writes through.
All admin endpoints below require:
  • JWT with role = SUPER_ADMIN
  • IpAllowlistGuard — caller IP must be in the operator allowlist
  • GeoBlockGuard — caller geo must be permitted
Calls that miss any of the three return 403.

When to use

POST /admin/telr/reconcile/:transactionId

Manually reconciles a single Telr transaction. Bypasses any env-level reconciliation gating (the endpoint is the recovery path of last resort). Accepts either:
  • The Telr cartid / txnref (issued at intent creation)
  • Our internal order ObjectId (24-char hex)
The handler resolves the supplied ID to the TelrTransaction, calls Telr’s /gateway/order.json to refetch settlement state, then writes through to the order and unified-transaction projection.

Authentication

Path parameters

Request body

Empty — POST with no body.

Response — 200 OK

Error responses

Example

Telr’s sandbox at secure.telr.com/gateway/order.json (with ivp_test=1) does not guarantee webhook delivery. The reconcile endpoint is the canonical recovery path for both sandbox testing and prod webhook outages.

Operational context

The reconcile endpoint exists because:
  1. Telr’s hosted checkout posts back to txnref callback URL after redirect — if the customer closes the tab before redirect completes, the webhook is the only signal.
  2. Telr’s webhook retry policy is short (3 attempts within 1 hour). After that, the order stays PENDING indefinitely unless an operator reconciles.
  3. Sandbox runs (ivp_test=1) frequently skip webhook delivery; reconcile is the only reliable way to confirm a test settled.
For systemic gaps (e.g., a sustained webhook outage), prefer the unified-transactions reconciliation cron over looping this endpoint by hand.