Buy-Now-Pay-Later Gateway Connector

Buy-now-pay-later has become a default tender at checkout across MENA and much of Asia, and it breaks the assumption every simple payment integration is built on: that the customer paying and the money arriving are the same event.

With BNPL they are not. The customer completes checkout and the order is authorised immediately. The provider assumes the credit risk and pays you later — often on a weekly or fortnightly cycle, always net of a merchant discount fee that is a percentage of order value, sometimes with a fixed per-transaction component and frequently with VAT applied to that fee. If the customer returns goods, the provider claws the amount back out of a future payout, which means a refund you issued in March can reduce a settlement in April. Meanwhile the customer's own installment schedule with the provider is none of your business and must never appear in your general ledger.

Posted naively, this produces a familiar mess. Sales Orders are marked paid against money that has not arrived, so cash forecasting is wrong. Revenue is booked gross while payouts land net, so the bank never reconciles. Refund clawbacks appear as unexplained negative adjustments. And because the provider payout is a single net figure covering dozens of orders across several days, nobody can say which orders it actually settled.

This connector is built to order for your NetSuite account. It is not a listed app you can install now. ECOSIRE scopes your checkout flow, your provider agreement and your chart of accounts, quotes a fixed price, then builds and installs a SuiteScript 2.1 SDF project in your sandbox before production.

What ECOSIRE builds

A tender type NetSuite understands

A dedicated Payment Method record and a custom transaction body field mark BNPL orders at the point of capture, so they are filterable in every saved search and report from day one. A User Event script on the Sales Order or Cash Sale writes the provider reference, the authorised amount, the plan term and the authorisation state onto the transaction.

Authorisation without pretending cash arrived

On authorisation the connector does not create a Customer Payment against your operating bank account. It posts to a BNPL receivable clearing account you nominate during scoping, so the ledger shows exactly what is true: the order is settled from the customer's perspective and the money is owed to you by the provider. That single decision is what makes cash forecasting and the eventual bank reconciliation work.

Webhook ingestion that survives retries

A RESTlet receives provider callbacks for authorisation, capture, cancellation, expiry, refund and settlement events. Signatures are verified with the N/crypto module before any record is touched. Every accepted event is written to a custom record with the provider event id in a unique field, so duplicate or replayed webhooks are recognised and discarded rather than creating a second payment. Heavy work is handed to N/task so the provider always gets a fast acknowledgement.

Deferred settlement matching

A Map/Reduce script pulls settlement reports from the provider API on your payout cycle and builds a Settlement Batch parent custom record with Settlement Line children — one per order, fee, VAT component, refund clawback or adjustment inside that payout. Lines are matched back to their originating transactions. The batch clears the BNPL receivable clearing account and creates the Deposit for the net amount actually hitting your bank, so Match Bank Data can clear it in one action.

Fees, VAT and clawbacks

Merchant discount fees, fixed per-order fees and any VAT charged on them post as a Journal Entry to the expense and tax accounts you nominate, with the correct nexus and tax code. Refund clawbacks are matched to the original Credit Memo or Customer Refund so the negative line in a later payout is explained rather than written off as an adjustment.

Cancellations, expiries and partial captures

An authorisation that expires or is cancelled before fulfilment reverses cleanly against the clearing account and updates the order state. Partial captures on partially fulfilled orders are supported where your provider allows them, with the residual authorisation tracked on the transaction.

Multi-entity, multi-currency and OneWorld

Provider credentials, clearing accounts, fee accounts, tax codes and bank accounts are configured per subsidiary on a custom record. Transactions are created against the correct subsidiary with the correct currency and exchange rate. A custom segment can be stamped on generated transactions so BNPL can be analysed as a channel alongside your other tenders.

Roles, monitoring and audit

A purpose-built integration role holds only the permissions the scripts need, and credentials live in NetSuite rather than in script constants. Saved searches surface stale authorisations, unmatched settlement lines, failed events and clearing-account balances that are ageing beyond your payout cycle. A Scheduled script emails a daily exception digest. Every posting links back to the raw provider event, so an auditor can trace any figure end to end.

Who this is for

Retail and D2C sellers in MENA or Asia running NetSuite where BNPL is already a meaningful share of checkout; omnichannel merchants who need BNPL orders reported alongside card and cash tenders; and finance teams whose provider payouts currently sit as unreconciled bank lines because no one can decompose them.

How delivery works

1. Scoping call. We review your checkout stack, your provider agreement and fee schedule, your payout cycle, refund policy, chart of accounts and subsidiary structure. 2. Fixed quote. You receive a written scope naming every record, script and posting we will build, with a fixed price and a delivery window. Work starts only on your approval. 3. Build. ECOSIRE develops the SuiteScript 2.1 project. Typical lead time is two to four weeks from approval, depending on scope, the number of providers and how quickly sandbox and provider test credentials arrive. 4. Sandbox install. The SDF project is deployed to your sandbox. We run authorisation, cancellation, expiry, refund, clawback and full settlement cycles against provider test mode with your team, and adjust until they sign off. 5. Production install. The same bundle is promoted to production, credentials are switched to live, and we supervise your first real payout reconciliation together. 6. Support window. A defined post-go-live support period for defect fixes and configuration changes is included in the quote.

What this is not

This is not an instant-download app, and ECOSIRE is not a partner, reseller or certified integrator of any BNPL provider. You hold your own merchant agreement, your own fee schedule and your own credit and consumer-protection obligations. We build the integration that gets those events into NetSuite correctly, delivered as source code you own.