# Axra

- [Introduction](https://docs.useaxra.com/introduction.md): Accept payments, move money, and build financial products with Axra
- [Quickstart](https://docs.useaxra.com/quickstart.md): Charge a card or create a Treasury partner in under 5 minutes
- [Authentication](https://docs.useaxra.com/authentication.md): Pass your API key in the x-api-key header or exchange it for a short-lived JWT token. Learn both authentication methods and how to obtain your credentials.
- [Error Codes](https://docs.useaxra.com/reference/error-codes.md): Payment error codes returned by the Axra API
- [Testing](https://docs.useaxra.com/reference/testing.md): Use sandbox API keys, test cards, and local webhook tunnels to fully validate your Axra Pay integration before switching to live credentials.
- [Changelog](https://docs.useaxra.com/changelog.md): Changes to the Axra API that can affect an existing integration.
- [Overview](https://docs.useaxra.com/payments/overview.md): Charge cards server-to-server, confirm 3DS challenges, retrieve payment details, list transactions, and issue refunds using the Axra Pay Payments API.
- [Checkout Sessions](https://docs.useaxra.com/payments/checkout-sessions.md): Create an Axra Pay hosted checkout page in one API call. Customers enter card details on Axra's secure page — no PCI DSS scope added to your integration.
- [Card Payments](https://docs.useaxra.com/payments/card-payments.md): Charge cards server-to-server with the Axra Payments API
- [Local payment methods](https://docs.useaxra.com/payments/local-payment-methods.md): Collect bank transfers, mobile money, and instant EFT — settled in USDC.
- [Local rails — hosted checkout](https://docs.useaxra.com/payments/local-rails-checkout.md): Accept bank, MoMo, and EFT through Axra's hosted checkout.
- [Local rails — server-to-server](https://docs.useaxra.com/payments/local-rails-api.md): Mint deposit instructions directly from your backend. No redirect required.
- [Payer return URL](https://docs.useaxra.com/payments/return-url.md): Set once where customers return after paying. Collections successUrl is ignored; S2S card returnUrl still works.
- [Local-rail payouts](https://docs.useaxra.com/payments/payouts/index.md): Send African bank transfers and mobile money payouts from your USDC balance using the Business Payouts API.
- [Payout quote](https://docs.useaxra.com/payments/payouts/quote.md): Lock FX for 60 seconds before confirming a local-rail payout.
- [Local payout corridors](https://docs.useaxra.com/payments/payouts/local-rails.md): Supported destination countries and recipient field requirements for LOCAL_BANK and LOCAL_MOMO payouts.
- [3D Secure (3DS)](https://docs.useaxra.com/payments/3ds.md): Add 3DS authentication to card payments for fraud reduction and liability shift
- [Overview](https://docs.useaxra.com/treasury/overview.md): Build banking products with Axra Treasury — KYC, wallets, payouts, and compliance
- [End-users](https://docs.useaxra.com/treasury/end-users.md): Create and manage end-users for your Treasury integration
- [KYC](https://docs.useaxra.com/treasury/kyc.md): Run identity verification for your end-users
- [Wallets](https://docs.useaxra.com/treasury/wallets.md): Create multi-currency wallets for your end-users
- [Payouts](https://docs.useaxra.com/treasury/payouts.md): Send money from end-user wallets to bank accounts, mobile money, or crypto
- [Sandbox](https://docs.useaxra.com/treasury/sandbox.md): Test your Treasury integration end-to-end without real money
- [Webhooks](https://docs.useaxra.com/manage/webhooks.md): Receive real-time HTTP callbacks for payment completions, refunds, disputes, and settlements. Learn how to verify signatures and handle events reliably.
- [Disputes](https://docs.useaxra.com/manage/disputes.md): Learn how chargebacks work on Axra Pay, how to retrieve dispute data via the API, and what steps you can take to reduce disputes and win them.
- [Settlements](https://docs.useaxra.com/manage/settlements.md): Understand the Axra Pay settlement lifecycle, fee deductions, and timeline for when captured payments are credited to your Axra merchant wallet.
- [Node.js SDK](https://docs.useaxra.com/sdks/node.md): Install @useaxra/node and start accepting payments in minutes
- [Python SDK](https://docs.useaxra.com/sdks/python.md): Install the axra Python package and integrate in minutes
- [Pay.js](https://docs.useaxra.com/sdks/pay-js.md): Embed secure, PCI-scoped card input fields directly in your payment form
- [CLI](https://docs.useaxra.com/sdks/cli.md): Login, forward webhooks locally, and trigger test events from the command line
- [List payout recipients for the active business](https://docs.useaxra.com/api-reference/payout-recipients/list-payout-recipients-for-the-active-business.md): Lists saved payout recipients for the active business, newest first. Archived recipients are hidden unless you pass `includeArchived`; filter by `rail` and page with `page` and `limit` (1 and 20 by default, `limit` capped at 100). Destination details come back masked.
- [Create a payout recipient](https://docs.useaxra.com/api-reference/payout-recipients/create-a-payout-recipient.md): Creates a saved recipient you can pay by `recipientId`. Idempotent on the destination: sending the same rail + account details returns the existing recipient instead of a duplicate. Dashboard (JWT) requests are sanctions-screened on create and a match is refused with 403. Server-to-server requests a…
- [Get a payout recipient by id](https://docs.useaxra.com/api-reference/payout-recipients/get-a-payout-recipient-by-id.md): Retrieves one saved recipient by id, with the destination details masked. Archived recipients are not returned — an archived id is a 404.
- [Archive a payout recipient (soft delete)](https://docs.useaxra.com/api-reference/payout-recipients/archive-a-payout-recipient-soft-delete.md): Archives a recipient. This is a soft delete: it drops out of the default listing and can no longer be fetched or paid, while payouts already sent to it keep their history. Idempotent — archiving an already archived recipient still returns 204.
- [Update recipient label](https://docs.useaxra.com/api-reference/payout-recipients/update-recipient-label.md): Renames a recipient. The label is the only mutable field: destination details are frozen at creation, so correcting an account number means creating a new recipient. An archived recipient cannot be updated.
- [List batch payouts for the active business](https://docs.useaxra.com/api-reference/payout-batches/list-batch-payouts-for-the-active-business.md): Lists batch payouts for the active business, newest first. Filter with `status` and page with `skip` and `take` (0 and 20 by default). Line items are not included — fetch a single batch for those.
- [Create a draft batch payout (payroll) + preview](https://docs.useaxra.com/api-reference/payout-batches/create-a-draft-batch-payout-payroll-+-preview.md): Validates up to BATCH_MAX_ITEMS line items, resolves each recipient (saved or inline — inline ones are sanctions-screened and saved), server-side quotes every item, and persists a DRAFT batch with child payouts in CREATED (not yet dispatched). Returns the per-item fee breakdown, summed totals, and a…
- [Submit a draft batch for processing](https://docs.useaxra.com/api-reference/payout-batches/submit-a-draft-batch-for-processing.md): Re-checks affordability against the live wallet balance, gates 2FA when the summed USD-equivalent >= $10k (dashboard path; api-key exempt), and transitions the batch DRAFT → QUEUED for the fan-out processor.
- [Get a batch payout with its line items](https://docs.useaxra.com/api-reference/payout-batches/get-a-batch-payout-with-its-line-items.md): Retrieves one batch with every line item: the per-item amounts, fees and payout status, plus the rows that failed to resolve at creation with the reason each failed, ordered by their index in the list you submitted.
- [Cancel a draft or queued batch](https://docs.useaxra.com/api-reference/payout-batches/cancel-a-draft-or-queued-batch.md): Allowed only while the batch is DRAFT or QUEUED and no item has been dispatched.
- [List scheduled payouts for the active business](https://docs.useaxra.com/api-reference/payout-schedules/list-scheduled-payouts-for-the-active-business.md): Lists scheduled payouts for the active business, newest first. Filter with `status` and page with `skip` and `take` (0 and 20 by default).
- [Create + authorize a scheduled payout](https://docs.useaxra.com/api-reference/payout-schedules/create-+-authorize-a-scheduled-payout.md): Validates the cadence (MONTHLY day-of-month 1–28, optional) and the per-run USD cap (defaults to $50k, rejected above the $250k admin ceiling), sanctions-screens every recipient in the payload, verifies the transaction PIN on the dashboard path (api-key exempt), stamps authorizedAt/By, and computes…
- [Get a scheduled payout](https://docs.useaxra.com/api-reference/payout-schedules/get-a-scheduled-payout.md): Returns the schedule plus a MASKED list of its recipients (`items[]`): label, rail, corridor (country · currency), and the configured per-run amount only. No account numbers / IBAN / phone and no partner names are exposed.
- [Edit (re-authorize) a scheduled payout](https://docs.useaxra.com/api-reference/payout-schedules/edit-re-authorize-a-scheduled-payout.md): Replaces the recipient list / amounts (new hire, resignation, raise) WITHOUT recreating the schedule — the cadence, day-of-month and nextRunAt timing are preserved. Every edit re-authorizes: it re-validates the payload + per-run cap, sanctions-screens every recipient in the new payload, re-verifies…
- [Cancel a scheduled payout](https://docs.useaxra.com/api-reference/payout-schedules/cancel-a-scheduled-payout.md): Sets status to CANCELLED (terminal). Idempotent on an already-cancelled schedule.
- [Pause / resume / rename a scheduled payout](https://docs.useaxra.com/api-reference/payout-schedules/pause-resume-rename-a-scheduled-payout.md): Only the status (ACTIVE↔PAUSED) and name are editable here (no PIN). Changing the payload or per-run amount requires re-authorization (PIN + screening) — use PUT /schedules/:id.
- [List supported banks / mobile money networks for a corridor](https://docs.useaxra.com/api-reference/payouts/list-supported-banks-mobile-money-networks-for-a-corridor.md): Returns the live upstream catalog filtered to status=active for the given country and rail. Pass the returned `id` back as the recipient `bankCode` (LOCAL_BANK) or `networkId` (LOCAL_MOMO).
- [Resolve a beneficiary name from a bank account number](https://docs.useaxra.com/api-reference/payouts/resolve-a-beneficiary-name-from-a-bank-account-number.md): Provider-neutral wrapper around the upstream account-name lookup. Returns the resolved holder name for the given (accountNumber, networkId).
- [Get a cross-currency payout quote (60s lock)](https://docs.useaxra.com/api-reference/payouts/get-a-cross-currency-payout-quote-60s-lock.md): Returns a signed quote token valid for 60 seconds. Pass the token to POST /v1/business/payouts within the window to lock the rate.
- [List payouts for the active business](https://docs.useaxra.com/api-reference/payouts/list-payouts-for-the-active-business.md): Lists payouts for the active business, newest first. Filter with `status` and `rail`, and page with `skip` and `take` (0 and 20 by default, `take` capped at 100). The response carries `total` alongside the page.
- [Initiate a business payout](https://docs.useaxra.com/api-reference/payouts/initiate-a-business-payout.md): Confirms a payout against a signed `quoteToken` (LOCAL_BANK / LOCAL_MOMO). Name the destination in exactly one of three ways: `recipientId` for a recipient saved via POST /v1/business/payouts/recipients; inline `recipient` to send the details on the payout itself; or, for requests authenticated with…
- [Get a single business payout](https://docs.useaxra.com/api-reference/payouts/get-a-single-business-payout.md): Retrieves one payout by id, scoped to the active business — a payout belonging to another business is a 404. Use it to follow a payout to its terminal state.
- [Cancel a CREATED payout](https://docs.useaxra.com/api-reference/payouts/cancel-a-created-payout.md): Cancels a payout that has not been dispatched yet. Only a payout still in CREATED can be cancelled; anything further along is a 409. The amount the attempt debited is reversed back to your balance.
- [Authenticate with business API key and secret](https://docs.useaxra.com/api-reference/authentication/authenticate-with-business-api-key-and-secret.md)
- [Regenerate API key](https://docs.useaxra.com/api-reference/authentication/regenerate-api-key.md)
- [Self-onboard a SANDBOX developer partner (authenticated; requires completed identity verification). TEST keys only.](https://docs.useaxra.com/api-reference/authentication/self-onboard-a-sandbox-developer-partner-authenticated;-requires-completed-identity-verification-test-keys-only.md)
- [Returns authenticated partner id (public contract surface)](https://docs.useaxra.com/api-reference/authentication/returns-authenticated-partner-id-public-contract-surface.md)
- [List merchant pricing per corridor (aggregated total fee, no provider breakdown)](https://docs.useaxra.com/api-reference/payments/list-merchant-pricing-per-corridor-aggregated-total-fee-no-provider-breakdown.md): The fee schedule in effect for your own account, aggregated to one total per corridor: a combined percentage in basis points, a fixed component and a fee floor, all in minor units of `feeCurrency`, and each row bounded by the amount band it applies to. Covers money-IN (collection) pricing only — pay…
- [Create a payment link](https://docs.useaxra.com/api-reference/payments/create-a-payment-link.md): Creates a one-off hosted payment page for a fixed amount and returns its URL together with the payment id to track it by; a `payment.created` webhook fires immediately. Reach for it when you want one hosted checkout without configuring a reusable link — `POST /business/links` is the reusable, branda…
- [Charge a card directly (server-to-server)](https://docs.useaxra.com/api-reference/payments/charge-a-card-directly-server-to-server.md): Charges a card server-to-server, with no redirect to a hosted page. Name the card in EXACTLY ONE of `card`, `savedTokenId`, `mpgsSessionId` or `walletToken`: the schema cannot express that constraint, and sending none or more than one is a 400. `customerIp` must be the IP address of the end customer…
- [Confirm 3D Secure authentication](https://docs.useaxra.com/api-reference/payments/confirm-3d-secure-authentication.md): Completes a charge that came back with `requiresAction`, once the payer has finished the 3-D Secure challenge. Key it on the `transactionId` the charge returned, not on the payment id. The response carries the verdict from the card platform, but only a failure is written back to the payment: a succe…
- [Get payment details](https://docs.useaxra.com/api-reference/payments/get-payment-details.md): Retrieves one payment by its Axra payment id, with card, customer, failure and authorisation detail normalised so the shape does not change with the rail that collected it. The projection is an allow-list: upstream identifiers and our own costs are never returned.
- [Refund a payment](https://docs.useaxra.com/api-reference/payments/refund-a-payment.md): Refunds a payment in full — there is no partial-refund parameter. The payment must be COMPLETED and no more than 180 days old; anything else is a 400. On success the payment moves to REFUNDED and a `payment.refunded` webhook fires carrying the refund id. If the refund is declined the response is a 4…
- [List payments](https://docs.useaxra.com/api-reference/payments/list-payments.md): Lists the payments on your account newest-first across every rail, paginated with `page` and `limit` (1 and 20 by default). Same allow-listed projection as retrieving a single payment.
- [Create a checkout session](https://docs.useaxra.com/api-reference/payments/create-a-checkout-session.md): Creates a hosted checkout session for one amount and returns `checkoutUrl` to send the payer to, valid for `expiresIn` seconds (one hour by default). If you include `card` or `savedTokenId` in the body the session is charged immediately instead and no `checkoutUrl` comes back — the response then rep…
- [List payment links](https://docs.useaxra.com/api-reference/payment-links/list-payment-links.md): Lists every payment link on the account, newest first, including deactivated ones (`isActive` false). Not paginated.
- [Create a payment link](https://docs.useaxra.com/api-reference/payment-links/create-a-payment-link.md): Creates a reusable hosted payment page at a slug you choose. The slug is global and must be 3 to 30 characters of lowercase letters, digits and hyphens, not starting or ending with a hyphen; a slug already taken is a 409. `amountType` decides what the payer may pay: `fixed` requires `fixedAmount`, `…
- [Deactivate a payment link](https://docs.useaxra.com/api-reference/payment-links/deactivate-a-payment-link.md): Deactivates a payment link. This is a soft delete: the link and its payment history are kept, but the hosted page stops resolving and returns 404 to payers. Reversible by sending `isActive` true to `PATCH /business/links/{id}`.
- [Update a payment link](https://docs.useaxra.com/api-reference/payment-links/update-a-payment-link.md): Updates presentation and amount configuration in place; only the fields you send change. The slug is fixed at creation and cannot be changed here. Setting `isActive` to true reactivates a deactivated link.
- [List customers](https://docs.useaxra.com/api-reference/customers/list-customers.md): Lists the customers you have collected from, derived from your own payment history, with the payment count and total collected for each. Paginated with `page` and `limit` (1 and 20 by default).
- [Find customer by email](https://docs.useaxra.com/api-reference/customers/find-customer-by-email.md): Finds a customer by the email address on their account and returns their customer id with aggregate totals. Returns 404 when no account carries that email, or when that account has never paid you.
- [Retrieve a customer](https://docs.useaxra.com/api-reference/customers/retrieve-a-customer.md): Retrieves one customer with their saved cards and their 20 most recent payments to you. The customer must have paid you at least once and must have a stored customer profile: a payer who has only ever paid without one returns 404.
- [Remove a payment method](https://docs.useaxra.com/api-reference/customers/remove-a-payment-method.md): Detaches a saved card from a customer so it can no longer be charged. A payment method that does not belong to that customer is a 400.
- [Set default payment method](https://docs.useaxra.com/api-reference/customers/set-default-payment-method.md): Marks one of the saved cards on a customer as the default for future charges. Send `paymentMethodId` in the body; a payment method that does not belong to that customer is a 400.
- [Get merchant dispute defence policy](https://docs.useaxra.com/api-reference/disputes/get-merchant-dispute-defence-policy.md): Returns the defence policy applied to your disputes: whether evidence is submitted automatically, the minimum win score required before it is, the amount and currency below which a loss is accepted without contest, and your default evidence text. A default policy is created on first read.
- [Update merchant dispute defence policy](https://docs.useaxra.com/api-reference/disputes/update-merchant-dispute-defence-policy.md): Updates the defence policy; only the fields you send change. Use it to turn automatic submission on or off, move the win-score bar, or set the amount below which contesting a dispute is not worth it.
- [Get dispute count summary (open / won / lost)](https://docs.useaxra.com/api-reference/disputes/get-dispute-count-summary-open-won-lost.md): Returns the open, won and lost dispute counts for your account. Cheaper than listing disputes when all you need is the headline numbers.
- [List disputes for the authenticated merchant](https://docs.useaxra.com/api-reference/disputes/list-disputes-for-the-authenticated-merchant.md): Lists disputes raised against your payments. `status` selects one of `open`, `won`, `lost` or `all` and DEFAULTS TO `open`, so pass `all` to see everything; narrow further with `currency`, `from` and `to`, and page with `page` and `limit`. Every response also carries the open, won and lost counts fo…
- [Get dispute detail for a payment](https://docs.useaxra.com/api-reference/disputes/get-dispute-detail-for-a-payment.md): Retrieves the dispute on one of your payments, keyed on the PAYMENT id rather than on a dispute id. Returns the payment, the dispute with its reason and evidence deadline, the evidence bundle assembled for it (null if there is none yet) and any files you uploaded. A payment carrying no dispute is a…
- [Upload merchant dispute evidence file](https://docs.useaxra.com/api-reference/disputes/upload-merchant-dispute-evidence-file.md): Uploads a supporting file for a dispute as multipart form data under the field name `file`, up to 5 MB. Files accumulate: each upload is added to the ones already on the dispute rather than replacing them. The payment must carry a dispute, or the request is a 400.
- [Accept dispute loss (merchant opts not to contest)](https://docs.useaxra.com/api-reference/disputes/accept-dispute-loss-merchant-opts-not-to-contest.md): Concedes a dispute without contesting it, for when the evidence would not win or the amount is not worth defending. The payment must carry a dispute.
- [List webhook endpoints for the business (API key)](https://docs.useaxra.com/api-reference/webhooks/list-webhook-endpoints-for-the-business-api-key.md)
- [Create a webhook endpoint (returns signing secret once)](https://docs.useaxra.com/api-reference/webhooks/create-a-webhook-endpoint-returns-signing-secret-once.md)
- [Replay a webhook delivery (queues a new delivery)](https://docs.useaxra.com/api-reference/webhooks/replay-a-webhook-delivery-queues-a-new-delivery.md)
- [Get a webhook endpoint](https://docs.useaxra.com/api-reference/webhooks/get-a-webhook-endpoint.md)
- [Delete a webhook endpoint](https://docs.useaxra.com/api-reference/webhooks/delete-a-webhook-endpoint.md)
- [Update a webhook endpoint](https://docs.useaxra.com/api-reference/webhooks/update-a-webhook-endpoint.md)
- [List deliveries for a webhook endpoint](https://docs.useaxra.com/api-reference/webhooks/list-deliveries-for-a-webhook-endpoint.md)
- [Rotate signing secret (returned once)](https://docs.useaxra.com/api-reference/webhooks/rotate-signing-secret-returned-once.md)
- [List treasury webhook endpoints for the authenticated partner](https://docs.useaxra.com/api-reference/webhooks/list-treasury-webhook-endpoints-for-the-authenticated-partner.md)
- [Create a treasury webhook endpoint (signing secret returned once)](https://docs.useaxra.com/api-reference/webhooks/create-a-treasury-webhook-endpoint-signing-secret-returned-once.md)
- [Replay a webhook delivery (queues a new delivery)](https://docs.useaxra.com/api-reference/webhooks/replay-a-webhook-delivery-queues-a-new-delivery-1.md)
- [Get a treasury webhook endpoint](https://docs.useaxra.com/api-reference/webhooks/get-a-treasury-webhook-endpoint.md)
- [Delete a treasury webhook endpoint](https://docs.useaxra.com/api-reference/webhooks/delete-a-treasury-webhook-endpoint.md)
- [Update a treasury webhook endpoint](https://docs.useaxra.com/api-reference/webhooks/update-a-treasury-webhook-endpoint.md)
- [List deliveries for a treasury webhook endpoint](https://docs.useaxra.com/api-reference/webhooks/list-deliveries-for-a-treasury-webhook-endpoint.md)
- [Rotate signing secret (returned once)](https://docs.useaxra.com/api-reference/webhooks/rotate-signing-secret-returned-once-1.md)
- [List fraud rules](https://docs.useaxra.com/api-reference/fraud/list-fraud-rules.md)
- [Create fraud rule](https://docs.useaxra.com/api-reference/fraud/create-fraud-rule.md)
- [Evaluate fraud rules against sample payload](https://docs.useaxra.com/api-reference/fraud/evaluate-fraud-rules-against-sample-payload.md)
- [Get fraud rule](https://docs.useaxra.com/api-reference/fraud/get-fraud-rule.md)
- [Delete fraud rule](https://docs.useaxra.com/api-reference/fraud/delete-fraud-rule.md)
- [Update fraud rule](https://docs.useaxra.com/api-reference/fraud/update-fraud-rule.md)
- [List blocked entities (merchant-scoped + platform-wide)](https://docs.useaxra.com/api-reference/fraud/list-blocked-entities-merchant-scoped-+-platform-wide.md)
- [Unblock a blocked entity (merchant-scoped only)](https://docs.useaxra.com/api-reference/fraud/unblock-a-blocked-entity-merchant-scoped-only.md)
- [List local-rails collections](https://docs.useaxra.com/api-reference/local-rails/list-local-rails-collections.md): Lists your local-rail collections newest-first, cursor-paginated: pass `limit` (1 to 100, 25 by default) and `starting_after` set to the id of the last collection on the previous page. `hasMore` says whether another page exists.
- [Create a local-rails collection (S2S)](https://docs.useaxra.com/api-reference/local-rails/create-a-local-rails-collection-s2s.md): Starts a local bank transfer or mobile money collection and returns the instructions the customer follows to pay. The currency must be enabled on your account and the corridor priced, or the request is refused as unsupported; a `momo` channel additionally requires `customer.phone`. Send an `idempote…
- [Retrieve a local-rails collection](https://docs.useaxra.com/api-reference/local-rails/retrieve-a-local-rails-collection.md): Retrieves one collection you own by id, with its current status and payment instructions.
- [Force-refresh a local-rails collection from the upstream provider](https://docs.useaxra.com/api-reference/local-rails/force-refresh-a-local-rails-collection-from-the-upstream-provider.md): Pulls the current state of a collection from upstream and returns the refreshed record, rather than serving the state last stored. Use it to reconcile when a webhook was missed; a collection already in a terminal state is returned unchanged with no upstream call.
- [List available local-rail channels](https://docs.useaxra.com/api-reference/local-rails/list-available-local-rail-channels.md): Lists the local-rail channels open to a `country`, `currency` and `amount`, all three required. Channels that cannot take that amount are returned separately with a `BELOW_MIN` or `ABOVE_MAX` reason alongside the corridor bounds, so a below-minimum amount reveals the floor instead of coming back emp…
- [Sandbox-only: manually approve pending KYC for an end-user](https://docs.useaxra.com/api-reference/treasury-—-kyc/sandbox-only:-manually-approve-pending-kyc-for-an-end-user.md)
- [Sandbox-only: manually reject pending KYC for an end-user](https://docs.useaxra.com/api-reference/treasury-—-kyc/sandbox-only:-manually-reject-pending-kyc-for-an-end-user.md)
- [Get current KYC status for an end-user](https://docs.useaxra.com/api-reference/treasury-—-kyc/get-current-kyc-status-for-an-end-user.md)
- [Initiate KYC verification for an end-user](https://docs.useaxra.com/api-reference/treasury-—-kyc/initiate-kyc-verification-for-an-end-user.md)
- [List treasury end-users](https://docs.useaxra.com/api-reference/treasury-—-end-users/list-treasury-end-users.md)
- [Create a treasury end-user](https://docs.useaxra.com/api-reference/treasury-—-end-users/create-a-treasury-end-user.md)
- [Get a treasury end-user by id](https://docs.useaxra.com/api-reference/treasury-—-end-users/get-a-treasury-end-user-by-id.md)
- [Soft-delete a treasury end-user (status CLOSED)](https://docs.useaxra.com/api-reference/treasury-—-end-users/soft-delete-a-treasury-end-user-status-closed.md)
- [Update a treasury end-user](https://docs.useaxra.com/api-reference/treasury-—-end-users/update-a-treasury-end-user.md)
- [Sandbox-only: credit a wallet for integration testing](https://docs.useaxra.com/api-reference/treasury-—-wallets/sandbox-only:-credit-a-wallet-for-integration-testing.md)
- [List an end-user's wallets](https://docs.useaxra.com/api-reference/treasury-—-wallets/list-an-end-users-wallets.md)
- [Provision a wallet for an end-user (currency-scoped)](https://docs.useaxra.com/api-reference/treasury-—-wallets/provision-a-wallet-for-an-end-user-currency-scoped.md)
- [Get wallet detail](https://docs.useaxra.com/api-reference/treasury-—-wallets/get-wallet-detail.md)
- [Get wallet balance from ledger](https://docs.useaxra.com/api-reference/treasury-—-wallets/get-wallet-balance-from-ledger.md)
- [Deposit instructions (fiat VA and/or crypto liquidation address)](https://docs.useaxra.com/api-reference/treasury-—-wallets/deposit-instructions-fiat-va-andor-crypto-liquidation-address.md)
- [Partner ledger entries for this wallet currency (paginated)](https://docs.useaxra.com/api-reference/treasury-—-wallets/partner-ledger-entries-for-this-wallet-currency-paginated.md)
- [List payouts for the authenticated partner](https://docs.useaxra.com/api-reference/treasury-—-payouts/list-payouts-for-the-authenticated-partner.md)
- [Initiate a payout from an end-user wallet](https://docs.useaxra.com/api-reference/treasury-—-payouts/initiate-a-payout-from-an-end-user-wallet.md)
- [Get payout by id](https://docs.useaxra.com/api-reference/treasury-—-payouts/get-payout-by-id.md)
- [Cancel a payout if it is still PENDING](https://docs.useaxra.com/api-reference/treasury-—-payouts/cancel-a-payout-if-it-is-still-pending.md)
- [Check which corridors are usable right now](https://docs.useaxra.com/api-reference/corridor-status/check-which-corridors-are-usable-right-now.md): Returns one row per country, currency, method and direction, saying whether you can collect or pay out over it at this moment. `status` reflects end-to-end usability through Axra, not just whether an upstream network is reachable — a corridor that is not enabled for your account reports `disabled` r…
- [Create an ephemeral Elements session (publishable key + amount + currency)](https://docs.useaxra.com/api-reference/elements/create-an-ephemeral-elements-session-publishable-key-+-amount-+-currency.md): Opens a short-lived tokenisation session for a browser payment form. It authenticates with your publishable key rather than a secret, so it is safe to call from the page: the key is resolved to an active account and a session id is returned with its lifetime in seconds. Rate-limited per publishable…
- [Tokenize card data for a session (iframe / allowed origins only)](https://docs.useaxra.com/api-reference/elements/tokenize-card-data-for-a-session-iframe-allowed-origins-only.md): Exchanges card details for a single-use token inside an open session, so the card number never reaches your own server. Callable only from an allow-listed origin — the browser `Origin` header is checked and a missing or unrecognised one is refused — and the session must still be live. Returns the to…

## OpenAPI Specs

- [openapi](/openapi.json)
- [openapi](/public/openapi.json)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.