Effortless integrations

Integrating with Ozow is simple! Check out the guides below to see the different integration methods. They’re listed from the easiest at the top, to the most difficult at the bottom.

Payment report request link

With this integration, you get full access to the Ozow portal, where you can easily and quickly create and send payment links to your customers. To generate a payment request, enter these details:

  • the payment amount,
  • customer’s name,
  • reference you expect on your bank statement (e.g. an invoice number),
  • and the payment link delivery method.

You can choose one of three different ways to send the payment link:

SMS: Ask for your customer’s cellphone number, and enter it into the payment request portal. Your customer will then receive an SMS with a payment link.

Email: Ask for your customer’s email address, and enter it into the payment request portal. Your customer will receive an email with a payment link.  

QR Code: You’ll get a unique Ozow QR code. Your customers can then scan this QR code with their device, and then be redirected to the payment process. You also have the option to create bulk payment request links. Bear in mind, this means that you will have to send the links out (Ozow only generates bulk payment links, we don’t distribute them). That being said, we also give you the option to make static or dynamic payment requests, and give you the power to specify the payment amount and/or bank reference. For this integration, you won’t need a website, coding skills or access to developers.

Http web form post

This integration method is a normal HTML form with text fields that are posted to Ozow. Your customer is redirected from your website to Ozow’s payment page – from there, they’ll go through the payment process. Once their payment is successful, Ozow redirects your customer back to your website, as set out by the callback URLs in the form’s post fields. Please note that there are a few optional fields that you can use, which you can find out more about by contacting support@ozow.com.

Through this integration, you'll need a few things, such as a website and a web developer with some knowledge of server-side scripting. To make sure the data you post is secure, a hash will also need to be generated server side, on the fly and posted through to Ozow with the form post fields. Generating a hash needs some server-side-scripting, so a small backend server is also needed.

JS injection

This integration method helps alleviate the need to redirect your customer. All you have to do is add a script file to your website. This will pull one of two simple payment screen types into your website:

1. iFrame: through iFrame, you'll have a degree of control over styling the payment screen. But it’s worth noting that iFrame is not compatible with all devices.

2. Modal: through Modal, you'll have pretty much no control over the UX and styling of the payment screen. However, Modal is compatible with all types of devices.

Through the JS injection integration method, you'll need a website and a web developer with some knowledge of front-end scripting. To make sure the data being posted is secure, a hash will also need to be generated server side, on the fly and posted through to Ozow with the form post fields. Generating a hash needs some server-side-scripting and therefore a small backend server is also required.

URL generation via API

Ozow also provides an integration method that generates a URL link via an API. All you need to do to set this up is call Ozow’s API, pass through a few data fields stipulating payment details, and identify yourself as the merchant.

Authorisation header fields need to be passed through to authenticate that you are, in fact, who you claim to be. To make sure data being passed remains secure, a hash needs to be generated, on the fly and posted through with the fields being sent through to Ozow’s API endpoint. We’ll then respond to successful API calls with a request ID and a payment link. The request ID can be used to check the status of the payment via an API call. You can then send the payment link to your customers in any of these convenient formats:

1. a button on a webpage or pdf invoice,

2. a link on a webpage or pdf invoice,

3. a QR code on a t-shirt, website, pdf invoice, banner, etc.,

4. or a link sent via SMS, email, USSD, in-app, etc. Take note that you'll be responsible for delivering and displaying the payment link. Aside from this, you’ll also need a back-end server, as well as a proficient back-end developer with front-end web skills.

Payment system plugins

Choose from our comprehensive list of plugins to make integrating Ozow into your business easy.

API integrations

For all the developers out there:

Step 1 - Post from Merchant Website

When your customer has made their purchase and selected Ozow as their payment method, you’ll need to post the following variables to https://pay.ozow.com.

Post variables

PROPERTY TYPE REQUIRED DESCRIPTION
1. SiteCode String (50) Yes A unique code for the site currently in use. A site code is generated when adding a site in the Ozow Merchant Admin section.
2. CountryCode String (2) Yes The ISO 3166-1 alpha-2 code for the user’s country. The country code will determine which banks will be displayed to the customer. Please note only South African (ZA) banks are currently supported by Ozow.
3. CurrencyCode String (3) Yes The ISO 4217 3 letter code for the transaction currency. Please note only South African Rand (ZAR) is currently supported by Ozow, so any currency conversion would have to take place before posting to the Ozow site.
4. Amount Decimal (9,2) Yes The transaction amount. The amount is in the currency specified by the currency code posted.
5. Transaction
Reference
String (50) Yes The merchant’s reference for the transaction
6. BankReference String (20) Yes The reference that will be prepopulated in the “their reference” field in the customer's online banking site. This will be the payment reference that appears on your transaction history.
7. Optional1
8. Optional2
9. Optional3
10. Optional4
11. Optional5
String (50) No Optional fields the merchant can post for additional information they would need passed back in the response. These are also stored with the transaction details by Ozow and can be useful for filtering transactions in the merchant admin section.
12. Customer String (100) No The customer's name or identifier.
13. CancelUrl String (50) No The Url that we should post the redirect result to if the customer cancels the payment, this will also be the page the customer gets redirect back to. This Url can also be set for the applicable merchant site in the merchant admin section. If a value is set in the merchant admin and sent in the post, the posted value will be redirected if the payment is cancelled.
14. ErrorUrl String (150) No The Url that we should post the redirect result to if an error occurred while trying to process the payment, this will also be the page the customer gets redirect back to. This Url can also be set for the applicable merchant site in the merchant admin section. . If a value is set in the merchant admin and sent in the post, the posted value will be redirected to if an error occurred while processing the payment.
15. SuccessUrl String (150) No The Url that we should post the redirected result to if the payment was successful, this will also be the page the customer gets redirect back to. This Url can also be set for the applicable merchant site in the merchant admin section. If a value is set in the merchant admin and sent in the post, the posted value will be redirected if the payment was successful. Please note that it would not be sufficient to assume the payment was successful just because the customer was redirected back to this page, it’s highly recommended the you check the response fields and check the transaction status using our check transaction status API call.
16. NotifyUrl String (150) No The Url that we should post the notification result to. The result will be posted regardless of the outcome of the transaction. This Url can also be set for the applicable merchant site in the merchant admin section. If a value is set in the merchant admin and sent in the post, the notification result will be sent to the posted value. Find out more in the notification response section in step 2.
17. IsTest bool Yes Send true to test your request posting and response handling. If set to true you will be redirected to a page where you can select whether you would like a successful or unsuccessful redirect response sent back. Please note that notification responses are not sent for test transactions and the online banking payment is skipped. Accepted values are true or false.
HashCheck String (250) Yes SHA512 hash used to ensure that certain fields in the message have not been already after the hash was generated. Check the generate hash section below for more details on how to generate the hash.
Property
Trype
Required
Description
1. SiteCode
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CountryCode
String (2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CurrencyCode
String (3)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
4. Amount
Decimal (9,2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
5. Transactionreferance
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
6. Bankreferance
String (20)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
7. optional1
8. optional2
9. optional3
10. optional4
11. optional5
String (50)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
12. Customer
String (100)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
13. CancelUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
14. ErrorUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
15. SuccessUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
16. NotifyUrl
String (150)
no
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
17. IsTest
bool
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
HashCheck
String (250)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section

Generate the Post Hash Check

Follow these steps to generate the hash check:

1. Concatenate the post variables (excluding HashCheck) in the order they appear in the post variables table.

2. Append your secret key to the concatenated string. Your secret key can be found in the merchant details

section of your admin site.

3. Convert the concatenated string to lowercase.

4. Generate a SHA512 hash of the lowercase concatenated string.

Step 2 - Process Ozow response

Ozow will send the following two posts back to you:

  • Redirect Response
  • Notification Response

Redirect Response

Depending on where in the payment process they are, we’ll redirect your customer to the applicable page with the response variables. Please note that if the applicable URL wasn’t sent in the post variables or set for your site in your admin site, your customer won’t be redirected back to your site along with the response variables.

The URL that is used is determined as follows:

  • Error URL: an error occurred during the payment process and payment was not successful.
  • Cancelled URL: the user chose to cancel during the payment process and payment was not successful.
  • Success URL: The payment was successful.

Use the hash response variable to verify the validity of the response (this process is further described in the response hash check section below). We recommended that you also use the notification response to verify the outcome of the transaction.

Notification Response

We will post the response variables to the designated notification URL. Please note that if the notification URL (NotifyUrl) was not sent in the post variables or set for your site in your admin site, we won't be able to send the notification post containing the response variables.

Use the hash response variable to verify the validity of the response, this process is further described in the response hash check section below.

Post variables

Property Type Description
1. SiteCode String (50) The site code sent to Ozow in the request post.
2. TransactionId String (50) The transaction identifier generated by Ozow
3. TransactionReference String (50) The merchant’s transaction reference sent in the request post’s TransactionReference variable.
4. Amount Decimal (9,2) The transaction amount. The amount is in the currency specified by the currency code posted.
5. Status String (50) The transaction status. Possible values are:

Complete – The payment was successful
Cancelled – The payment was cancelled
Error – An error occurred while processing the payment
6. Optional1
7. Optional2
8. Optional3
9. Optional4
10. Optional5
String (50) Optional fields sent in the request post.
11. CurrencyCode String (3) The transaction currency code sent in the request post.
12. IsTest bool Whether or not the original request was a test request. Possible values are

true

or

false
13. StatusMessage String (150) Message regarding the status of the transaction. This field will not always
have a value.
Hash String (100) SHA512 hash used to ensure that certain fields in the message have not been already after the hash was generated. Check the generate hash section below for more details on how to validate the response variables using the hash.
Property
Trype
Required
Description
1. SiteCode
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CountryCode
String (2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CurrencyCode
String (3)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
4. Amount
Decimal (9,2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
5. Transactionreferance
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
6. Bankreferance
String (20)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
7. optional1
8. optional2
9. optional3
10. optional4
11. optional5
String (50)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
12. Customer
String (100)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
13. CancelUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
14. ErrorUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
15. SuccessUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
16. NotifyUrl
String (150)
no
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
17. IsTest
bool
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
HashCheck
String (250)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
Response Hash Check

Follow these steps to generate the hash check:

1. Concatenate the post variables (excluding HashCheck) in the order they appear in the post variables table.

2. Append your secret key to the concatenated string. Your secret key can be found in the merchant details section of your admin site.

3. Convert the concatenated string to lowercase.

4. Generate a SHA512 hash of the lowercase concatenated string.

Compare generated hash to the Hash value in the response variables.

Step 3 - Check transaction status using API

This step is optional, but we highly recommend it – it helps ensure that the received responses reflect the correct transaction status. This will remove any chance of anyone spoofing the Ozow response to update a transaction status on your site. Each API call needs an http header value with the your API Key.

There are two API methods you can use to check the transaction status:

  • Get transaction by reference
  • Get transaction

Get transaction by reference

https://api.ozow.com/GetTransactionByReference?siteCode={siteCode}&transactionReference={transactionReference}  
Call this method when you want to query transactions using your reference. This method can return multiple results as Ozow doesn’t stop you from sending duplicate merchant references. However, we advise that a unique reference is sent for each transaction. The number of results returned is limited to 10.

Parameters

PROPERTY TYPE REQUIRED DESCRIPTION
ApiKey (Http request header value) String (50) Yes Merchant’s API key, this value is available in the Ozow Merchant Admin section.
Accept (Http request header value) String (50) Yes Determines the format the response is returned in, available values: application/json – Response is returned as json application/xml – Response is returned as xml
SiteCode String (50) Yes A unique code for the each of the merchant’s sites. A site code is generated when adding a site in the Ozow Merchant Admin section.
Transaction
Reference
String (50) Yes The merchant’s reference for the transaction
IsTest bool No Defaults to false. Use true only to get results for test requests.


A successful call will return an array of the transaction object, which is described further down.

Get transaction

https://api.ozow.com/GetTransaction?siteCode={siteCode}&transactionId={transactionId}
Call this method when you want to query transactions using Ozow’s reference.

PROPERTY TYPE REQUIRED DESCRIPTION
ApiKey (Http request header value) String (50) Yes Merchant’s API key, this value is available in the Ozow Merchant Admin section.
Accept (Http request header value) String (50) Yes Determines the format the response is returned in, available values: application/json – Response is returned as json application/xml – Response is returned as xml
SiteCode String (50) Yes A unique code for the each of the merchant’s sites. A site code is generated when adding a site in the Ozow Merchant Admin section.
TransactionId Decimal (50) Yes Ozow’s reference for the transaction. This would be passed back to the merchant in the redirect and notification responses.


A successful call will return an array of the transaction object, which is described further down.

Transaction object

This is the object referred to in the response of the 2 API calls above.

PROPERTY TYPE DESCRIPTION
TransactionId String (50) Ozow’s unique reference for the transaction.
MerchantCode String (50) Unique code assigned to each merchant.
SiteCode String (50) Unique code assigned to each merchant site.
TransactionReference String (50) Merchant’s transaction reference.
CurrencyCode String (3) The transaction currency code
Amount Decimal (9,2) The transaction amount.
Status String (50) The transaction status. Possible values are: Complete – The payment was successful Cancelled – The payment was cancelled Error – An error occurred while processing the payment
StatusMessage String (150) Message regarding the status of the transaction. This field will not always have a value.
CreatedDate DateTime Transaction created date and time
PaymentDate DateTime Transaction payment date and time
Property
Trype
Required
Description
1. SiteCode
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CountryCode
String (2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CurrencyCode
String (3)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
4. Amount
Decimal (9,2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
5. Transactionreferance
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
6. Bankreferance
String (20)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
7. optional1
8. optional2
9. optional3
10. optional4
11. optional5
String (50)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
12. Customer
String (100)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
13. CancelUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
14. ErrorUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
15. SuccessUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
16. NotifyUrl
String (150)
no
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
17. IsTest
bool
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
HashCheck
String (250)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
Merchant Post

Step 1 - Post from Merchant Website

When your customer has made their purchase and selected Ozow as their payment method, you’ll need to post the following variables to https://pay.ozow.com.

Post variables

Property
Trype
Required
Description
1. SiteCode
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CountryCode
String (2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CurrencyCode
String (3)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
4. Amount
Decimal (9,2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
5. Transactionreferance
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
6. Bankreferance
String (20)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
7. optional1
8. optional2
9. optional3
10. optional4
11. optional5
String (50)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
12. Customer
String (100)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
13. CancelUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
14. ErrorUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
15. SuccessUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
16. NotifyUrl
String (150)
no
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
17. IsTest
bool
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
HashCheck
String (250)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section

Generate the Post Hash Check

Follow these steps to generate the hash check:

1. Concatenate the post variables (excluding HashCheck) in the order they appear in the post variables table.

2. Append your secret key to the concatenated string. Your secret key can be found in the merchant details section of your admin site.

3. Convert the concatenated string to lowercase. 4. Generate a SHA512 hash of the lowercase concatenated string.

Ozow Response

Step 2 - Process Ozow response

Ozow will send the following two posts back to you:

  • Redirect Response
  • Notification Response

Redirect Response

Depending on where in the payment process they are, we’ll redirect your customer to the applicable page with the response variables. Please note that if the applicable URL wasn’t sent in the post variables or set for your site in your admin site, your customerwon’t be redirected back to your site along with the response variables.

The URL that is used is determined as follows:

  • Error URL: an error occurred during the payment process and payment was not successful.
  • Cancelled URL: the user chose to cancel during the payment process and payment was not successful.
  • Success URL: The payment was successful.

Use the hash response variable to verify the validity of the response (this process is further described in the response hash check section below). We recommended that you also use the notification response to verify the outcome of the transaction.

Notification Response

We will post the response variables to the designated notification URL. Please note that if the notification URL (NotifyUrl) was not sent in the post variables or set for your site in your admin site, we won't be able to send the notification post containing the response variables.

Use the hash response variable to verify the validity of the response, this process is further described in the response hash check section below.

Post variables

Property
Trype
Required
Description
1. SiteCode
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CountryCode
String (2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CurrencyCode
String (3)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
4. Amount
Decimal (9,2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
5. Transactionreferance
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
6. Bankreferance
String (20)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
7. optional1
8. optional2
9. optional3
10. optional4
11. optional5
String (50)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
12. Customer
String (100)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
13. CancelUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
14. ErrorUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
15. SuccessUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
16. NotifyUrl
String (150)
no
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
17. IsTest
bool
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
HashCheck
String (250)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
Response Hash Check

Follow these steps to generate the hash check:

1. Concatenate the post variables (excluding HashCheck) in the order they appear in the post variables table.

2. Append your secret key to the concatenated string. Your secret key can be found in the merchant details section of your admin site.

3. Convert the concatenated string to lowercase. 4. Generate a SHA512 hash of the lowercase concatenated string.

Compare generated hash to the Hash value in the response variables.

API Status

Step 3 - Check transaction status using API

This step is optional, but we highly recommend it – it helps ensure that the received responses reflect the correct transaction status. This will remove any chance of anyone spoofing the Ozow response to update a transaction status on your site. Each API call needs an http header value with the your API Key.

There are two API methods you can use to check the transaction status:

  • Get transaction by reference
  • Get transaction

Get transaction by reference

https://api.ozow.com/GetTransactionByReference?siteCode={siteCode}&transactionReference={transactionReference}  
Call this method when you want to query transactions using your reference. This method can return multiple results as Ozow doesn’tstop you from sending duplicate merchant references. However, we advise that a unique reference is sent for each transaction. The number of results returned is limited to 10.

Parameters

A successful call will return an array of the transaction object, which is described further down.

Get transaction

https://api.ozow.com/GetTransaction?siteCode {siteCode} &transactionId={transactionId}
Call this method when you want to query transactions using Ozow’s reference.

A successful call will return an array of the transaction object, which is described further down.

Transaction object

This is the object referred to in the response of the 2 API calls above.

Property
Trype
Required
Description
1. SiteCode
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CountryCode
String (2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
2. CurrencyCode
String (3)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
4. Amount
Decimal (9,2)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
5. Transactionreferance
String (50)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
6. Bankreferance
String (20)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
7. optional1
8. optional2
9. optional3
10. optional4
11. optional5
String (50)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
12. Customer
String (100)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
13. CancelUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
14. ErrorUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
15. SuccessUrl
String (150)
No
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
16. NotifyUrl
String (150)
no
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
17. IsTest
bool
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section
HashCheck
String (250)
Yes
A unique code for the site currently in use. A code is generated when adding a site in the ozow marchant admin section