Transactions

Every payment created through the API — by your backend, by the sandbox simulator, or by another tool using the same API key — appears in Open Finance → Transactions.

The list view

The table shows the most recent payments with:

• Transaction ID (the same one the API returns).
• Merchant reference.
• Amount and currency.
• Current status — see Status values below.
• Destination bank.
• Initiation and last-updated timestamps.

Filter by status, date range, destination, or free-text search against reference and transaction ID.

Status values

The detail view

Click any row to see:

• The Mastercard payment ID and raw Mastercard status — useful when opening a support ticket.
• The destination bank, the API credential that initiated the payment, and the redirect / flow URLs issued to the customer.
• The metadata you passed at initiation, decoded and rendered.

For an authoritative state check, call GET /v1/payments/{transactionId}. The dashboard reflects the same record.

Investigating a failed payment

1. Open the transaction.
2. Look at the Mastercard status — that's the raw upstream reason (for example CANCELLED or REJECTED).
3. Compare against your own webhook log. ARYZE retries failed deliveries up to four times (1s / 5s / 15s); if your endpoint never returned 2xx, the transaction status in the dashboard is still authoritative.
4. Still unclear? Contact support with the ARYZE transaction ID and Mastercard payment ID.

Reconciling

For bulk reconciliation, compare transaction IDs and final status against your own order table. Everything in the dashboard maps 1:1 to what GET /v1/payments/{transactionId} returns, so you can automate reconciliation with the API and keep the dashboard for ad-hoc investigation.