Prerequisites
Confirm the following before APIWorx provisions the connector. Each item maps to a configuration step that cannot be completed without it, so a gap here stops setup partway through rather than at first sync.- Admin access to your PayWay merchant account, used to authorize the API credentials the connector reads from.
- Admin access to your DualEntry company, used to authorize the connection and confirm account mappings.
- Open invoices in DualEntry Accounts Receivable that carry the same order or invoice reference passed through PayWay, so payments can match to the right invoice.
- A bank or clearing account and a fee or expense account set up in your chart of accounts, so net cash and processing fees each have a target account.
- An APIWorx engagement for the DualEntry + PayWay connector. APIWorx hosts and operates the connector; the setup steps below are completed with your APIWorx implementation contact.
How the connector works
The connector moves payment activity from PayWay into DualEntry in a single direction through APIWorx. A payment, refund, or settlement event in PayWay triggers the sync; APIWorx reads the transaction, separates the gross amount from the processing fee, matches the payment to an open DualEntry invoice, and posts the cash application and fee entry. Webhooks drive near real time syncs where PayWay exposes them, and a configurable polling interval covers everything else. APIWorx runs the connector as a managed service on its own infrastructure, with continuous monitoring and logging. You do not host or run anything yourself, and there is no PayWay connector tile inside the DualEntry application. Account mappings and the match-key selection are maintained through APIWorx rather than in DualEntry. The connector performs six jobs on each synced transaction:- Transaction capture. Retrieves authorized, captured, and settled transactions from PayWay, including transaction ID, amount, currency, timestamp, payment method, and the customer or order reference.
- Fee separation. Reads the gross amount, processing fee, and net settlement amount, then splits them so the fee posts to the configured fee account and net cash posts to the configured bank or clearing account.
- Payment-to-invoice matching. Matches each PayWay payment to an open DualEntry AR invoice using the order or invoice reference as the primary key, with amount-and-date matching as a fallback.
- Cash application. Applies the matched payment against the invoice, marking it paid or partially paid and recording the deposit to the clearing or bank account.
- Refund handling. Captures refunds and chargebacks from PayWay and posts the corresponding credit or reversal entry against the original transaction.
- Settlement reconciliation. Groups individual transactions into the PayWay settlement batch or payout so the deposit recorded in DualEntry matches the actual bank deposit amount.
How payments match to invoices
The connector matches each PayWay payment to an open DualEntry invoice so cash is applied to the right receivable rather than posted as an unallocated deposit. Matching runs on two keys in priority order, and you choose the behavior during configuration. The primary key is the order or invoice reference passed through PayWay. When your checkout or billing flow sends the DualEntry invoice reference with the payment, the connector applies the payment to that exact invoice. This is the reliable path, so populate the reference field wherever you can. The fallback is amount-and-date matching. When no usable reference is present, the connector looks for an open invoice whose amount and date align with the payment. A fallback match is less certain than a reference match, so confirm these against your AR ledger during the first few sync cycles. The connector also separates each transaction into three amounts before posting: the gross amount applied against the invoice, the processing fee posted to the fee account, and the net settlement deposited to the bank or clearing account. Because the fee is posted separately, the invoice is settled at its gross amount and the fee appears as its own expense line rather than reducing the cash applied to the customer’s balance.What syncs into DualEntry
The connector imports four kinds of PayWay activity: payments, processing fees, refunds, and settlement groupings. Each payment becomes a cash application against an AR invoice, paired with a fee entry, so the resulting records behave the same as a manually entered customer payment in DualEntry. The table below summarizes what flows from PayWay into DualEntry on each sync:Field mapping
The connector maps each PayWay transaction field to a DualEntry field during posting. The mapping below is representative; your APIWorx configuration sets the exact account targets and match key for your chart of accounts.
The account targets (AR, bank or clearing, and fee) and the match-key selection are the settings you maintain over time. When you restructure these GL accounts, update the corresponding mapping in APIWorx so payments continue to post to the correct accounts.
Configure the connection
Set up the connector with your APIWorx implementation contact. APIWorx authorizes both systems and records the account mappings and match key the connector applies on every sync. Work through the items below in order; the mappings depend on the connections being authorized first.- Authorize the PayWay connection. Provide the PayWay API credentials for your merchant account so the connector can read transactions, fees, and settlements.
- Authorize the DualEntry company connection. Connect APIWorx to the DualEntry company that receives the postings.
- Map the target accounts. Choose the AR account, the bank or clearing account for net deposits, and the fee or expense account for processing fees.
- Select the match key. Choose whether the connector matches on the order or invoice reference (recommended) with amount-and-date as a fallback, and confirm currency handling.
- Set the sync mode. Use webhook-driven syncing where PayWay supports it, or set a polling interval (for example, every 15 minutes, hourly, or daily) where it does not.