Get Transaction By Reference
Try it
Parameters
Request sample
curl -X GET 'https://api.ozow.com/GetTransactionByReference?siteCode=TST-MER-001&transactionReference=MyReference&isTest=false' \
-H 'ApiKey: YOUR_API_KEY'Response example
Built from the response schema. Values are placeholders, not real data.
https://api.ozow.com/GetTransactionByReferenceProductionBuild with AI 2 packages
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.
- Embed checkout in your own pageEverything needed to keep the customer on your site while they pay, as an iframe, a modal, or the Wallet SDK for Apple Pay and Google Pay, with the notification that actually confirms the payment.
- Migrate a payin from the Payments API to One APIEverything needed to move an existing redirect payin onto One API, with the legacy guide and its One API counterpart side by side.
This operation is used when you want to query transactions using the merchant's transaction reference, specified when creating the payment request. This method is able to return multiple results. Ozow does not restrict the merchant from sending duplicate merchant references, though it is advised that a unique reference is sent per transaction. The number of results returned are limited to 10. Note that the site codeSite code The 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. must be the same as the one used when the associated payment request was created.
Authentication
- API key in the ApiKey header
The unique API key for the merchant. See Prerequisites and onboarding for where to find it.
Query parameters
siteCodestring requiredA unique code for the each of the merchant's sites. A site codeSite code The 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.
max length50exampleTST-MER-001transactionReferencestring requiredThe merchant's reference for the transaction.
max length50exampleMyReferenceisTestbooleanDefaults to false. Use true only to get results for test requests.
examplefalse
Request body
This method is called when you want to query transactions using the merchant's reference. This method is able to return multiple results. Ozow does not restrict the merchant from sending duplicate merchant references, though it is advised that a unique reference is sent per transaction. The number of results returned are limited to 10.
Responses
application/json
application/xml
API key is missing or invalid.Merchant for site code TSTSTE0001 is deactivatedGuides
- Payin test casesThe payments to run before you go live on the Payments API, what each one delivers, and a notification handler that survives all of them.
- Redirect to OzowBuild a redirect payin on the Payments API, the legacy path. Post the payment, redirect the customer, and handle the notification response.