Known limitations

What the API does not do yet, so you can plan around it.

• Every gateway adapter is built from that gateway's public documentation and is checked against its live sandbox before production use. The sandbox signup links get you to a door, but the field-level integration is worth double-checking per gateway. FluidPay's production API host is not publicly documented yet, only its sandbox host, and NMI's Collect.js bank-account fields and Customer Vault saving have not been confirmed against a live NMI sandbox.
• Saved payment methods and hosted checkout on the invoice pay page work for 8 gateways: Stripe, PayPal, Braintree, Square, Adyen, Authorize.Net, FluidPay and NMI. See Saved payment methods.
• ACH / eCheck bank-account payments work for 6 gateways (Stripe, Authorize.Net, Braintree, NMI, Square and FluidPay). A later ACH return or dispute is not acted on automatically once PayMidWare has recorded a charge as successful. See ACH / eCheck payments.
• Schedules have no edit endpoint: cancel one and create a new one. BigCommerce and WooCommerce import only orders that are already paid. See Scheduled and recurring payments and Accounting, CRM and store sync.
• QuickBooks sync assumes the connected company runs in a single currency, and a company on QuickBooks automated sales tax may show a different tax total. See QuickBooks Online sync.
• The point of sale add-on has no public API. It takes cards by keyed entry, a saved card or QR code, with no swipe or tap reader yet and no offline mode. Every sale it completes can be copied to an invoice, so it shows up in the API.
• Connecting an accounting system, CRM or online store needs that system's own sign-in screen, so it is always done in the Portal, not through the API.