Overview

Netcash – Pay Now eCommerce is a secure online payment service that can be integrated into various applications to receive payments. It is currently being used for online stores, quotations, statements, and invoices to receive payment. We currently offer 3D secure Credit Card payments through Mastercard, Visacard, American Express, and Diners Club^*, instant EFT powered by OZOW, bank EFT, cash payments powered by SCode, -and Masterpass. Additional payment options will be extended over time, but no further development will be required by yourself.

^{*Please note – American Express / Diners Club available only on special request and by approval.}

Also see:

• View Pay Now Request service
• View Pay Now Billing service
• View Pay Now QR/POS service

See the service overview here.

Suggested Integration Process Flow

We highly recommend that you download the suggested API integration process flow document and keep it on hand while you develop.

Kindly adhere to the Netcash brand guidelines when developing.

Web Service Methods

The list of Netcash web service methods can be found here

QuickStart Guides

We have developed some Quick Start Guides to help you understand this service and to help you get started.

Programmers Guide

To start, refer our Programmers guide for more detail on how to apply the required methodology in this document.
Please ensure that the settings for Developers are correctly set before you proceed with the implementation below specification.

Service set up process

• • Specify the payment options you require on application for the service.
  • The Netcash merchant has to issue a Pay Now service key and;
    • make the required payment options available in the NetConnector profile -and
    • set the NetConnector profile with the required postback URL’s.
      • Download the Quick Start Guide here
  • NOTE: If you developing on behalf of a Netcash merchant, supply the merchant with the postback URL’s they need to insert in the NetConnector profile for you to consume after the transaction was processed.
  • Recommended Implementation Methodology:
    Develop the form POST method from your system with attribute target=”_top” to send the payment instruction to https://paynow.netcash.co.za/site/paynow.aspx to open the link in the full body of the current window.
    • Alternatively, develop the form POST method from your system with no target attribute to send the payment instruction to open https://paynow.netcash.co.za/site/paynow.aspx in itself. ^{(NB! This method is not advisable due to cross browser compatibility especially for Microsoft Edge and Apple Safari browsers – read more)}
    • See the demo files here

IMPORTANT: Do not process the form post in an iFrame -or embedded into any other page/system source; as certain services will not process unless opened in a parent window due to banking regulations -and/or security protocols.

• • Download the Pay Now logos to use on your payment gateway pages in your eCommerce store.

Credit Card transaction processing notice

Please take note that any new Pay Now eCommerce service has a default transaction limit of R100.00. If the transaction limit (ZAR value) is exceeded – Credit Card payment options will not display. Contact your Netcash Payments Advisor for assistance.

Pay Now payment methods

The payment methods available on the Pay Now service is available here or see the visual representation here.

Read more about the different payment methods we offer.

Pay Now service key

The service key is used to authenticate access to the Pay Now service. It identifies the origin of the payment instruction. The service key determines the Netcash account to which the proceeds of the payment will be credited and what payment options are available to your customer/s.

NetConnector

Your NetConnector profile setting allows you to customize the Pay Now service according to your requirements:

• Active: Indicates the service setting.
• Email: This is the email address to which any errors in processing will be directed. It is also the address to which the service key will be sent. Notifications of transactions will also be sent to this address.
• Service Key: This is the unique service key (field m1) which must be included in the POST to the Netcash URL.
• Allow Master and Visa payments: This option is used to control whether your client may pay by credit card.
• Accept url: Enter your accept URL here. If the URL changes for any reason, it can be updated on this page. This is the URL that the browser is sent to if the transaction is successful.
• Decline url: Enter your decline URL here. If the URL changes for any reason, it can be updated on this page. This is the URL that the browser is sent to if the transaction is declined.
• Notify url: This is the URL that Netcash will call for all transactions to indicate payment status. It is also used for offline transactions such as bank EFT and retail payments where the payment is not able to be captured in real time. These payments will be picked up when they are made and Netcash will notify your system through this URL.
• Redirect url: This is the URL that the browser is sent to once the complete button is clicked on the EFT and Retail payment screens on Netcash. This could/would return the customer to your site while you are waiting for a payment to be made.
• Make test mode active: use this setting while you are testing the system to simulate transactions. Once your development is complete, this box should be un-ticked
• In TEST MODE use the following credit card numbers to test with:

Configure Netcash – Pay Now service key variables:

Select ACCOUNT PROFILE -> NetConnector -> PAY NOW in your Netcash merchant account to configure your Netcash – Pay Now variables.

Pre-defined postback URLs

The Pay Now configuration allows the configuration of pre-defined postback URL groups.

These postback URLs perform two (2) functions namely:

1. They send data back to the host system about the transaction, especially useful for real-time notifications/allocation of credits.
   1. Once the transaction is processed, the status and the transactional data of the payment gets redirected to two pages:
      1. The Notify URL always receives all the transaction data but it is not client-facing -and
      2. The Accept -or Decline URL depending on the transaction status which;
2. The Accept -or Decline URL redirects the person making the payment, to a visual display of the transaction status once the transaction is completed.

You will note a Redirect URL in the list as well. This URL is used for when the user click’s the CANCEL PAYMENT button on the payment page -or when the user selects a non-real-time payment; to remind the user of i.e. the payment reference to use.

Netcash offers several payment options which the user can enable/disable in the Pay Now configuration.

Read more about pre-defined postback URL groups here.

You will note that the URLs, in this case, were set up by the merchant as to where the notifications post the processing of the transaction, should be sent.

Netcash also has a facility whereby the merchant can select from a dropdown menu, rather than the input (possibly incorrectly) a pre-defined set of URLs, which has been pre-set by Netcash as defined by the ISV. This will minimize the risk of incorrect postbacks. It is only applicable if the ISV software allows for, and uses the same URLs for all its installations at all the merchants – where a central server handles the postbacks and sends the responses to the various installations.

In such a case, Netcash will send the responses to the centralized server and the merchant simply selects the software from the drop-down list and Netcash handles the postback of data

POST to the Pay Now page:

See the recommended implementation methodology here.
These parameters are required by the Pay Now system when submitting a transaction. Although data is not mandatory for all the fields; all the fields must be passed in the form post.

The Netcash system will authenticate the Pay Now service key in field m1.
Only if the key is authenticated, will the payer be directed to the payment method selection page.

TIPS

• * Add the purchaser’s name -and the order/invoice number in brackets after the description to easily identify the transaction on your Netcash statement without looking at Pay Now transaction reports.
• ** Add the debtor’s reference in this field, please note – this does not display on the Netcash on screen statement, but is downloadable using the Netcash statement download.

Additional data

• See the recommended implementation methodology here.
• Please make sure that there is a cent amount in your post i.e. Post 12.00 rather than 12 as your amount. This is so that the 3D secure process gets the amount correct. Also do not post more than 2 decimal places like 12.0000 as your amount.
• Any data which you need to be returned to you in the Notify, Accept or Decline post should be included in m4, m5 or m6.
• Data in these fields will be returned in the Extra1, Extra2 and Extra3 fields of the post.
• Extra1, Extra2 and Extra3 fields will also be included in the export of your Netcash statement for reconciliation purposes.

Example

<form name="form" id="x1" method="POST" action="https://paynow.netcash.co.za/site/paynow.aspx" target="_top"> <!---Form POST **--->
  <input type="text" name="M1" value="7XXX34c4-XXX-40X8-9f1d-7fbXXXX830d3">  <!--- YOUR PAY NOW SERVICE KEY GOES IN HERE --->
  <input type="text" name="M2" value="24ade73c-98cf-47b3-99be-cc7b867b3080">  <!--- SOFTWARE VENDOR KEY GOES IN HERE --->
  <input type="text" name="p2" value="ID:123">                                <!---Unique ID for this / each transaction--->
  <input type="text" name="p3"  value="Test / Demo goods">                    <!---Description of goods being purchased--->
  <input type="text" name="p4" value="5.00">                                  <!---Amount to be settled / paid--->
  <input type="text" name="Budget" value="Y">                                 <!---Compulsory should be Y--->
  <input type="text" name="m4" value="Extra 1">                               <!---This is an extra field ***--->
  <input type="text" name="m5" value="Extra 2">                               <!---This is an extra field ***--->
  <input type="text" name="m6" value="Extra 3">                               <!---This is an extra field ***--->
  <input type="text" name="m9" value="myemail@email.net">                     <!---Card holders email address--->
  <input type="text" name="m11" value="0812345678">                           <!---Card holders mobile number--->
  <input type="text" name="m10" value="Demo attempt for testing">             <!---Dataset used by shopping carts i.e. OSCommerce--->
  <input type="text" name="m14" value="1">                                    <!---Request credit card subscription token 0 = no | 1 = yes--->
  <input type="text" name="m15" value="11ad173c-9d3f-43b3-19se-as7b865e3099"> <!---Credit card token for subscription cards--->
  <input type="text" name="m16" value="1">                                    <!---Subscription indicator 0 = no | 1 = yes--->
  <input type="text" name="m17" value="6">                                    <!---Number of cycles for subscription payment--->
  <input type="text" name="m18" value="1">                                    <!---Subscription frequency--->
  <input type="text" name="m19" value="2021-01-01">                           <!---Subscription start date --->
  <input type="text" name="m20" value="15.00">                                <!---Subscription recurring amount--->
  <input name="submit" type="submit" value="PAY">                             <!---Submit button--->
</form>

VERY IMPORTANT

• ** POST must be to a PARENT WINDOW – target=”_top” – not in an iFrame. Netcash offers some Pay Now services in an iFrame from our suppliers for security reasons. Modern browsers do not allow for iFrame within an iFrame on the same page. See Cross Frame Scripting article as to why not.
• *** extra field – you can place any data in the extra field which will be returned

Pay Now payment selections

^{click image for a demonstration}

• The payer selects the method of payment (credit card in this example) and is directed to the payment input page.

The payer is now redirected to the bank 3D Secure input screen where he/she enters the OTP sent to his/her email and/or mobile device – depending on bank setup – to authorize the transaction.

If the user selects Retail, the following is displayed which the user can print, email or SMS to himself to make a retail payment-

-or BANK EFT the following is displayed to enable the payer to make a bank-on-bank EFT (selecting Netcash (PTY) Ltd as predefined bank beneficiary)

The EFT payment details are displayed with a unique payment reference which must be used to make the EFT payment.

Notify, Accept, Decline and Redirect pages

After the transaction is complete the following data is returned to these respective pages which was configured in the Pay Now configuration. Read more about the Postback URL’s.
It is highly advisable that all developers reconcile (indicate payment status) from the data sent to the NOTIFY url.
This URL is called for all transactions asynchronously. Unlike Instant EFT and Credit Card services, delayed services like Retail -and Bank EFT do not call the Accept and Decline URL, however, all the services do send a notification to the Notify URL.
There is also a retry plan built into the Notify URL allowing to retry a number of times before it is noted as not received.
This should be utilized for system updates whereas Accept and Decline URL’s should be used to synchronously update the Buyer on the status of the transaction.

TIP: Remove the [FromUri] attribute from your endpoint signature.

Acceptable URL Format

When the accept, decline or notify URLs are called, any data provided in the M10 field will be appended to the URL. URLs that already contain query parameters are not supported and may lead to invalid URLs being formed. Do not include query parameters in the URLs using the query separator (“?” in the URL).

Netcash PayNow appends a query separator (“?”) to the URL followed by the M10 field contents.

Example:

The M10 field can be used for any additional transaction identifying information. The merchant should ensure that the contents of the M10 field are acceptable URL query parameters. Also consider using the Extra1 (M4), Extra2 (M5) and/or Extra3 (M6) fields for similar information.

Notify URL

Data URL is form POST.

content-type: application/x-www-form-urlencoded

Accept URL

Decline URL

Redirect URL

Testing

See Testing section for more details. If you require any integration assistance contact our technical support team