A build package is every page for one task, with the API operations they use. Copy the prompt into a coding assistant, or hand it the package itself: slim links to each page, full inlines all of them in one document.
Send a payoutEverything needed to pay money out to a customer's bank account or voucher with the Payouts API, including how to exercise the failure paths before going live.
This method can be called to retrieve the set of banks that are available for making payoutsPayoutMoney sent from a merchant to a bank account. Unlike a refund, a payout is not tied to a payment anyone made you, so you can pay anyone with a bank account. Payouts draw on your float rather than on your incoming payments, and they are not self-service: they need approval from Ozow and testing in staging first. to.
The call returns a list of banks with a unique identifier (BankGroupId) per bank. The BankGroupId is utilised as an input parameter to check payout availability for a particular bank, as well as to identify the destination bank for a payout.
Authentication
API key in the ApiKey header
Query parameters
rtconlyboolean
For RTCReal-Time ClearingPayments that clear immediately rather than waiting for a batch. A batch run settles at set times through the day; a Real-Time Clearing payment moves the funds between the two bank accounts as it is made, so the recipient can rely on them straight away.PayInc Banks only you can add the "rtconly" parameter to return a filtered list.
Header parameters
SiteCodestringrequired
A unique code for the site currently in use. A site codeSite codeThe unique code for a site registered under a merchant. A site is a place to transact: a website, or a branch of a store. A merchant can have several, and each transaction names the one it belongs to, so sending the wrong code files the payment against the wrong place. is generated when adding a site in the Ozow merchant admin section. [Please contact support for SiteCode - support@ozow.com]
max length50
exampleYOUR_SITE_CODE
Responses
200OK
array of BankGroup
400Bad Request. The request did not reach the API. A required header or query parameter is missing, or the body does not match the expected shape.
messagestring
What was wrong with the request.
403Forbidden. The SiteCode and ApiKey pair was not accepted.
messagestring
What was wrong with the request.
500Internal Server Error. The gateway could not reach the service or the integration failed. A failure inside the service is not this one. Those come back as a 200 with the reason in the payload, because the gateway maps every integration response it has no other rule for onto 200.