Solutions
Four solution areas, one integration.
Pay-in, pay-out, verification and the API infrastructure that ties them together — 15 capabilities in Payaura V1, all reached through the same API and delivered through integrated providers.
How to read this page
A capability within the scope of Payaura V1, delivered through integrated payment or verification service providers.
Beyond V1. Listed so the direction is visible, and not part of what is being built now.
Payaura is under development and nothing listed here is live on this website. Nothing on this page is an offer, a commitment to a launch date, or a representation that any approval or provider arrangement has been obtained.
01 — 4 capabilities
Pay-In
Accept and process incoming payments through integrated providers.
The pay-in layer gives a business one integration for collecting money. Payaura handles the provider connections, the transaction lifecycle and the record of what happened, so your application deals with a single consistent interface instead of one integration per provider.
- Payment collectionV1 scope
Accept incoming payments through integrated payment service providers, using one request format regardless of which provider fulfils it.
V1 scope- Transaction statusV1 scope
Query the current state of any transaction, with a consistent status model across providers.
V1 scope- WebhooksV1 scope
Receive server-to-server notifications as transactions move through their lifecycle, rather than polling for changes.
V1 scope- Ledger entriesV1 scope
Every movement is written to a double-entry ledger, so balances and history reconcile rather than drift.
V1 scope
02 — 4 capabilities
Pay-Out
Initiate outbound payouts through integrated banking and payment providers.
The pay-out layer is for businesses that need to send money — vendor payments, partner settlements, refunds, disbursements. The same integration, the same status model and the same ledger discipline as pay-in, pointed the other way.
- Payout initiationV1 scope
Initiate outbound transfers through integrated banking and payment service providers.
V1 scope- Beneficiary handlingV1 scope
Submit and reference payout destinations through the API as part of a payout request.
V1 scope- Payout status and webhooksV1 scope
Track a payout to completion or failure, with notifications on state changes.
V1 scope- Balance and settlement trackingV1 scope
See what has moved, what is pending settlement and what has settled, from one place.
V1 scope
03 — 4 capabilities
Verification
PAN and supported verification checks through integrated provider APIs.
Verification is where onboarding either works or stalls. Payaura exposes supported verification capabilities through the same API surface as payments, so a business can validate a counterparty and pay them without wiring up a second vendor relationship.
- PAN verificationV1 scope
PAN verification through integrated verification service providers, returned in a standardised response.
V1 scope- Verification API accessV1 scope
The same authentication, request shape and error model as the payment endpoints.
V1 scope- Verification recordsV1 scope
Each check is logged against your account so results can be retrieved and audited later.
V1 scope- Additional verification checksFuture expansion
Further verification categories are intended to be added as provider integrations are completed.
Future expansion
04 — 4 capabilities
API Infrastructure
One integration, and the orchestration layer that sits behind it.
This is what makes the other three usable. Rather than integrating each provider separately and maintaining that work forever, a business integrates Payaura once. The routing, the provider differences and the operational record are handled behind a single API.
- Unified REST APIV1 scope
One set of endpoints and one response format across pay-in, pay-out and verification.
V1 scope- API authenticationV1 scope
Key-based authentication with credentials managed from your dashboard.
V1 scope- Multi-provider orchestrationV1 scope
A routing layer that decides which integrated provider handles a request, so provider changes do not become integration work.
V1 scope- Reconciliation and reportingV1 scope
Transaction records, settlement tracking and reconciliation views across every capability you use.
V1 scope
Which of these do you need first?
Most integrations start with one capability and add the others later. Tell us what you need to collect, pay out or verify and we will scope it with you.