TransactNow sends payment instructions to supported banks.
Submit each payment as one REST request. You choose the payment rail and supply the receiving bank and account. TransactNow submits the instruction through that rail and returns its status to your application.
One instruction, tracked to a final status.
Submit the payment instruction
Your system sends the payment details to the TransactNow REST API as one request per payment.
TransactNow validates it
The instruction is checked against the format of the payment rail you selected.
TransactNow submits it
The instruction goes to the bank through that payment rail, and TransactNow tracks it to a final status.
Your application reads the status
The status comes back in the API response, and you can query it through the transaction history endpoint.
You choose the payment rail.
A payment rail is a bank-specific integration. You select the rail and supply the receiving bank and account, and TransactNow converts the instruction into that rail’s submission format. Availability by bank, payment type and channel, including PayShap, is confirmed during onboarding.
Authentication
Requests use an API key, a secret and the client certificate registered for your account, over mutual TLS.
Duplicates and validation
A duplicate submission returns 409 and a validation failure returns 422, so your system can handle both without guessing.
Status
Each payment moves from pending to submitted to a final success or failure state.
Where teams use it.
Corporate and supplier payments
Supplier, operational and customer payments across supported banks.
Property groups
Supplier payments, agent commissions, refunds and other property disbursements.
Automotive dealers
Stock purchases, supplier payments, customer refunds and commissions.
Insurance
Claims payouts, premium refunds and other customer disbursements.
Gaming and betting
Winnings and withdrawals, with PayShap where the bank offers it.
Lending
Disburse approved loans or other customer funds once approval is complete.
Marketplaces and gig platforms
Pay sellers, drivers, contractors and service providers.
Discuss your integration.
Describe the use case. We will map it to the relevant product and integration path.