Transactions

Reconciled inflows and their statuses.

Every reconciled inflow is written as an immutable transaction. The list is your ledger — statuses reflect the reconciliation rule book.

Unknown-account deposits go to review

A transfer into a NUBAN Xental doesn't recognise is still recorded (with a null account) and marked PendingReview rather than dropped — check the review queue for these.

High risk routes to review even when the amount matches

A deposit that reconciles on amount can still be flagged PendingReview if its risk score crosses the threshold (name mismatch, velocity, payer-name reuse).

Overpayments can be refunded

When a customer overpays (or pays twice), refund the surplus with POST /transactions/{reference}/refund. Pair it with an Overpaid → Hold rule to park the surplus for review first.
get/api/v1/transactions

List transactions, filtered by date range, status, reconciliation, or accountRef.

Requires Bearer token

Query parameters

fromstring<date-time>optional
tostring<date-time>optional
statusTransactionStatusoptional
reconciliationReconciliationStatusoptional
accountRefstringoptional
takeintegeroptional

Responses

200OK
GET /api/v1/transactions
curl -X GET "https://api.xental.online/api/v1/transactions" \
  -H "Authorization: Bearer <API_TOKEN>"
get/api/v1/transactions/summary

Pay-ins summary (total / successful / failed) for the dashboard cards, optionally scoped to a date range. Usable from the dashboard or an API key.

Requires Bearer token

Query parameters

fromstring<date-time>optional
tostring<date-time>optional

Responses

200OK
GET /api/v1/transactions/summary
curl -X GET "https://api.xental.online/api/v1/transactions/summary" \
  -H "Authorization: Bearer <API_TOKEN>"
get/api/v1/transactions/{reference}

Fetch a single transaction by its provider reference.

Requires Bearer token

Path parameters

referencestringrequired

Responses

200OK404Not Found
GET /api/v1/transactions/{reference}
curl -X GET "https://api.xental.online/api/v1/transactions/:reference" \
  -H "Authorization: Bearer <API_TOKEN>"
post/api/v1/transactions/{reference}/refund

Refund an overpayment surplus back to the payer (dashboard Owner/Admin). Sends only the amount still held for the account; releases any overpayment hold on success. Idempotent per deposit.

Refunds an overpayment surplus back to the payer. Sends only the amount still held for the account (never double-spends against settlement), releases any overpayment hold, and is idempotent per deposit. The destination is pre-filled from the payer’s captured source account, or supply accountNumber + bankCode.

Requires Bearer token

Path parameters

referencestringrequired

Body parameters

accountNumberstringoptional
bankCodestringoptional
accountNamestringoptional

Responses

200Refund sent (or already sent).400No refundable surplus, nothing available (already settled), or missing destination.404Not Found409A refund for this deposit is already in progress.
POST /api/v1/transactions/{reference}/refund
curl -X POST "https://api.xental.online/api/v1/transactions/:reference/refund" \
  -H "Authorization: Bearer <API_TOKEN>"