Understand payments.
Build with confidence.

A software interface used to request an operation or retrieve data from another system.

The person or business designated to receive a payment.

An incoming payment a business receives from a customer or payer.

A QR code generated for a particular payment request, typically carrying order-specific payment details.

A provider-hosted page where a customer completes the payment journey.

A saved identifier that lets a provider recognise repeat submissions of the same instruction under its API contract.

National Electronic Funds Transfer: an electronic transfer system that processes instructions in batches.

Your business reference for an order, distinct from the provider’s payment identifier.

Technology that connects a merchant’s payment experience with payment processing and returned results.

A shareable link that gives a customer access to a payment request.

An outgoing business payment to a recipient, such as an approved supplier payment.

An intermediate payment state; it should not be assumed to mean either final success or failure.

Comparing business, provider and bank records, then investigating and explaining differences.

A return of funds associated with an earlier payment, tracked with its own request and result.

Real Time Gross Settlement: transfers settled individually in real time, rather than netted in batches.

The transfer of funds between the relevant payment participants or accounts under the applicable arrangement.

Unified Payments Interface, the instant payment system developed by NPCI.

Unique Transaction Reference. Its format and use depend on the rail; an RTGS UTR has 22 characters.

An HTTP event notification delivered to an endpoint in your application.