Retry the accounting writeback for a charge

post

https://api.benjipays.com/v2/transactions/{transactionId}/retry-accounting

Retries only the accounting writeback (QBO / Xero / Business Central) for a charge that already succeeded — for example when POST /v2/transactions returned meta.effects.charge.status=succeeded with meta.effects.accounting.status=failed. The payment method is never charged again, the charge is never voided, and no receipt is sent.

Eligibility is read from the saved transaction, so a single call also tells you when there is nothing to write back. HTTP 200 always returns the current transaction in data plus meta.effects.accounting:

succeeded — applied. data carries the accounting payment id and paymentApplied.
failed — the accounting system is still unavailable. Safe to retry later.
skipped — nothing to apply. data.status says why (for example approved_voided when the charge was auto-voided after the original apply failed), or accounting was already applied, or the apply is deferred until a bank payment completes.

Requires organizations:transactions:create and a required Idempotency-Key header. Charges that cannot be retried at all (declined, no invoice, wrong type) return RFC 7807.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

transactionId

string

required

length ≤ 50

Transaction identifier — data.id from POST /v2/transactions or a GET /v2/transactions row (24-character hex). Unknown or malformed ids return 404.

Headers

X-Request-ID

uuid

Optional client-supplied unique ID for one request. The server generates a UUID v4 if omitted and always echoes the value in the response.

X-Correlation-ID

uuid

Optional ID that flows across service boundaries for distributed tracing. The server generates a UUID v4 if omitted and always echoes the value in the response.

Idempotency-Key

string

required

length between 1 and 255

^[a-zA-Z0-9]+$

Required client-supplied key that makes retries safe for this endpoint. Scoped per actor; cached for 24 hours. Replays return the cached response with X-Idempotency-Replayed: true. Same key with a different body returns 409. Missing key returns 400. In-flight duplicates return 429 with Retry-After. See the Idempotency section in the API overview.

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

200Retry evaluated. Inspect meta.effects.accounting (succeeded, failed, or skipped) and data for the current transaction state.

401Unauthorized

403Forbidden — missing required OAuth scope (organizations:transactions:create), insufficient live mapping permission on the API key owner (e.g. companyAdmin), and/or free trial ended without billing enabled. Scope, mapping, and billing state are independent gates; see response detail.

404Not found — unknown or malformed transaction id, or the transaction belongs to another organization.

409Idempotency key conflict (same key, different body), or the invoice is already being processed.

429Too Many Requests (rate limit or idempotency in-flight)

503Idempotency protection is temporarily unavailable, so the retry was not attempted. Retry the same request with the same Idempotency-Key after Retry-After seconds.