The main cost drivers are whether Worldpay's SuiteApp meets your needs or if you'll need custom development for complex settlement scenarios. The SuiteApp handles summary posting of daily settlement files well, but Worldpay's unique fee structures—with separate interchange, scheme fees, and chargeback line items—often require custom SuiteScript for transaction-level matching.

While NetSuite has some native Worldpay support through NSPOS for point-of-sale setups, broader ERP implementations typically need the SuiteApp or API integration, especially if you're processing through Worldpay's Corporate Gateway across multiple currencies and MIDs. High-volume merchants needing tokenization or recurring billing across entities usually find the SuiteApp's summary-level approach insufficient, driving up implementation complexity.

Worldpay often settles in a different currency than the original transaction. The integration records both the transaction currency and the settlement currency, along with the conversion rate Worldpay applied. NetSuite calculates the FX gain or loss and posts it to the appropriate account.

Each fee type posts to its own GL account: interchange, scheme fees, Worldpay processing charges. You can report on them individually or roll them up by payment method.

The integration picks up chargeback notifications from Worldpay and creates a credit memo or journal entry against the original transaction in NetSuite. The reason code is captured so you can report on dispute patterns. If the chargeback is reversed later, that reversal posts too.

Typically 6 to 8 weeks. The first couple of weeks cover scoping: mapping Worldpay's settlement file structure to your NetSuite chart of accounts, defining how fees should post, and setting up chargeback handling rules. Build and testing runs four to six weeks after that, including a parallel period where automated postings are validated against your existing manual reconciliation.

Worldpay nets transactions before settling, so a single bank deposit covers hundreds of sales minus refunds, chargebacks, and fees. The integration breaks that batch apart and matches each component to the corresponding NetSuite record. Your deposit reconciliation ties out at the transaction level, not the lump sum.

Yes. If you're on OneWorld and Worldpay settles to different bank accounts per region or entity, the integration routes each settlement to the correct subsidiary. Currency, GL mapping, and fee allocation are configured per entity during scoping.

No. The integration works with settlement and transaction metadata from Worldpay, not raw card data. No PANs or CVVs pass through the integration layer.