GCC Payment Gateway Connector (Tap)

The problem

Finance teams in the Gulf collect money through a regional gateway and record it in NetSuite by hand. A settlement notification arrives, someone opens the gateway dashboard, finds the transaction, works out which invoice it belongs to, creates a Customer Payment, and hopes the reference was typed correctly. Multiply that across several countries, several currencies and several merchant accounts and the aged receivables report stops being trustworthy.

NetSuite's built-in payment processing options are oriented toward North American and European acquirers. The local debit schemes that most Gulf customers actually pay with, the regional wallets, and the settlement currencies used across Saudi Arabia, the UAE, Kuwait, Bahrain, Oman, Qatar, Jordan and Egypt are not represented. So payments arrive outside NetSuite, and NetSuite finds out later.

What ECOSIRE builds

This is a build-to-order engagement: we build a payment gateway connector as a native NetSuite customization inside your own account, using your gateway merchant credentials. It is not a hosted service you rent and not a pre-packaged product you download.

Payment capture from NetSuite transactions

A Suitelet renders a hosted payment session for a Sales Order or Invoice, so the customer completes payment on the gateway's own page and no card data ever touches NetSuite. On success the connector writes a Customer Payment applied to the correct Invoice, or a Customer Deposit against the Sales Order where you take money before fulfilment. The gateway charge ID, authorization code, scheme, last four digits and issuing country are stored in custom body fields for audit.

Payment links for collections

For invoices sent by email, a User Event script generates a hosted payment link and stamps it on the Invoice record and its transaction email template. Your collections team can send a link from the Invoice itself instead of dictating bank details over the phone. A Scheduled script expires stale links and refreshes them on request.

Webhooks and settlement

A RESTlet published under a dedicated integration role receives gateway webhooks for authorization, capture, failure, refund, chargeback and dispute events. Every payload is signature-verified, written to a logging custom record, and processed idempotently by gateway event ID, so a retried webhook can never create a duplicate Customer Payment. A Map/Reduce script reconciles the daily settlement batch: gross amounts, gateway fees and any FX difference are posted to the accounts you nominate, and the resulting Deposit ties out to the amount that hit the bank.

Refunds and reversals

Customer Refunds and Credit Memos raised in NetSuite can trigger a full or partial refund at the gateway through SuiteFlow, subject to your approval routing. The gateway response is written back to the NetSuite transaction, so a refund is never marked complete in the ledger before the gateway has accepted it.

Multi-country and OneWorld

Each merchant account is bound to a subsidiary, so a Saudi entity and a UAE entity settle to their own books, their own accounts and their own currencies. Transaction currency and exchange rate are set on inbound payments, and custom segments are populated so payment activity flows into the same reporting dimensions as the rest of your ledger. Where a country requires the payment reference on a fiscal document, we write it onto the transaction so the two records stay linked.

Security and operations

Credentials live in a secured custom record using NetSuite's secrets support and are never exposed in script logs. The integration role carries only the permissions it needs. Every API call and webhook is logged with its request, response and outcome, and a saved search plus reminder surfaces failed or unmatched payments to a queue your team can work rather than leaving them silent.

Who this is for

Gulf and wider MENA sellers who take card and wallet payments online or by payment link and want the cash to land in NetSuite automatically. It suits B2C and B2B operations alike: subscription and service businesses invoicing in NetSuite, distributors collecting on account, and multi-country groups running OneWorld with separate merchant accounts per entity.

How delivery works

1. Scoping call. We review your gateway merchant setup, the countries and currencies in play, your invoicing flow, your fee accounts, and how you want unmatched payments handled. 2. Fixed quote. A written scope and a fixed price, agreed before any code is written. 3. Build. Development happens in a Sandbox account as an SDF project under source control, typically two to four weeks depending on the number of merchant accounts and the settlement mapping. 4. Install in test. The bundle is installed in your Sandbox and exercised end to end against gateway test credentials — authorization, capture, decline, partial refund, chargeback and settlement — with your finance team watching the resulting NetSuite postings. 5. Production. After sign-off the same SDF project is deployed to production, live merchant credentials are configured, webhooks are pointed at the production RESTlet, and we watch the first live settlement cycles with you. 6. Support. A post-go-live support window covering defects and gateway API changes encountered during that period.

You own the SDF project and its source. There is no per-transaction charge from us; you keep your own commercial relationship with the gateway and your acquirers.