CentraPoint

Gateways

Netcash Debit Orders

Recurring bank debit orders (NIF batches, e-mandates) and automated account reconciliation from Netcash merchant statements.

On this page

Recurring bank debit orders (NIF batches, e-mandates) and automated account reconciliation from Netcash merchant statements.

At a glance#

Netcash Debit Orders summary
Typenetcash
CountriesSouth Africa
CurrenciesZAR
CapabilitiesDebit ordersStatement reconciliation
Gateway docsapi.netcash.co.za/

Configuration fields#

Enter these in the dashboard under Settings → Payment providers → Netcash Debit Orders. Secret fields are encrypted at rest and masked after saving; leave a secret blank when editing to keep the stored value.

Netcash Debit Orders configuration fields
FieldTypeNotes
Debit order service keyrequired
debitOrderServiceKey
Secret

Netcash > Account profile > NetConnector > Debit orders

Account service keyrequired
accountServiceKey
Secret

Option group Account reconciliation. Netcash > Account profile > NetConnector > Account service. Used for merchant statements (reconciliation)

Software vendor key
softwareVendorKey
Text

Leave as default unless Netcash issued you an ISV key

Debit instruction
instruction
Choice

Options: Two-day (submit 2 business days before action date); Same-day (submit before cut-off on action date)

Default: TwoDay

Batch look-ahead (days)
batchLookaheadDays
Number

Batch mandates due within this many days

Default: 3

Mark collected after (days)
settleDays
Number

Accepted entries become 'complete' this many days after the action date unless an unpaid arrives

Default: 3

Auto-authorise batches via API
autoAuthorise
Checkbox

Only if enabled on your Netcash profile; otherwise authorise in the Netcash portal

Default: false

Mandate postback secret
postbackSecret
Secret

Append ?secret=<value> to the mandate postback URL configured in Netcash

Statement postback secret
statementPostbackSecret
Secret

Option group Account reconciliation. Netcash does not sign statement postbacks. Generated automatically when left blank; the Statement postback URL on the gateway card already includes it. A new secret means pasting the new URL into the Netcash portal.

Charge saved cards as card debit orders
cardDebits
Checkbox

Option group Card debits. Off by default. Switch on only once Netcash has enabled debit orders to cards ("Allow DO to card") on this debit order service. Cards are charged on the next debit order run (same day or two day, as set above).

Default: false

Every provider also has Enabled, Sandbox / test mode switches.

Notification URL#

Notification URL
https://app.centrapoint.co.za/api/webhooks/netcash?provider={providerId}

Copy the exact URL, with your provider ID filled in, from Settings → Payment providers.

  • Debit orders do not use the payment notification URL. Batches, upload reports and merchant statements are exchanged with Netcash's NIWS web service using your service keys.
  • Mandate status postbacks use a separate URL: in Netcash (Debit orders → Mandate postback URL) set /api/netcash/mandate-postback?provider=<providerId>&secret=<Mandate postback secret>. Copy it from Settings → Payment providers.
  • Account reconciliation: with the Account service key set, the gateway card also shows a Statement postback URL. In the Netcash portal open Account profile → NetConnector (Connected services) → Account service, tick postback and paste the URL: when Netcash signals a new statement, CentraPoint fetches it from Netcash at once. The nightly statement fetch stays on as the fallback. Netcash keeps one postback URL per account: for gateways that share an Account service key, paste the URL of any one of them.

How notifications are verified#

  • Batch and statement data is requested from Netcash by CentraPoint over NIWS (authenticated by your service keys). The only inbound calls are postbacks.
  • Statement postbacks are not signed: they are accepted only with the secret in the Statement postback URL (constant-time comparison), and nothing posted is reconciled: the statement is always fetched from Netcash first. A posted statement Netcash does not confirm is shown for review only.
  • Netcash does not sign mandate postbacks, so the Mandate postback secret is mandatory: postbacks without the matching secret are rejected with 403.
  • The amount and currency must match the transaction before it can be marked complete.

Going live#

  1. Test with sandbox credentials and Sandbox / test mode on, and confirm the notification appears as processed in the Webhook log.
  2. Replace the credentials with live ones and switch off Sandbox / test mode.
  3. Update any URL or secret configured in the gateway's portal for the live environment.
  4. Make a small live payment and confirm it with the Transactions API.