Server Payment API

Coming soon: a separate trusted-server receipt and refund connection.

Server Payment API · Coming soon

The planned trusted-server feed uses a separate named, expiring payments:write token. Stripe is the live revenue integration. Report API and MCP access require a paid plan; read credentials cannot write payments.

Planned receipt format

Once released, your server must first verify the payment with its provider. The planned format includes stable transaction and event IDs, exact integer minor units, currency, occurrence timestamp and explicit livemode. This test-mode example is a reference, not a live connection or payment request.

curl "https://zijra.com/api/v1/websites/YOUR_WEBSITE_ID/payments" \
  -H "Authorization: Bearer YOUR_PAYMENT_WRITE_TOKEN" \
  -H "Content-Type: application/json" \
  --data '{"transactionId":"order_001","eventId":"receipt_001","kind":"payment","amountMinor":9900,"currency":"USD","occurredAt":"2026-09-30T12:00:00Z","livemode":false}'

Refunds and attribution

Use kind: "refund", the original transaction ID and a stable distinct refund event ID. Import the receipt first; retries keep their IDs. Optional visitorId also requires consent: true and a matching stored consented visitor. Unmatched payments stay unassigned. Revoke the writer token when removing the integration.