Choose your integration path
Select a payment flow, assign responsibilities, and define the first implementation milestone.
Start with the customer workflow
For a new online integration, the recommended path is the NMI Payment Component plus the REST Payments API. The browser collects the payment method inside hosted fields and returns a token. Your application server submits the token with the authoritative order amount. Betterpay coordinates the commercial relationship and gateway provisioning; the documented software packages and API belong to NMI. online
Choose the smallest complete flow
Choose based on the experience your customers need, rather than the number of endpoints available. Route Use when Your implementation Payment Component + REST Checkout should remain inside your product Mount fields, implement server processing, confirmation and reconciliation Hosted Checkout A redirect to a hosted page fits the workflow Use the merchant’s generated checkout URL and reconcile the result Existing Collect.js You already have a working tokenization integration Keep the browser flow while evaluating server migration In-person integration Customers present a card or phone at a device Confirm device, processor and platform compatibility before development
Agree responsibility before writing code
A gateway account does not automatically enable every payment method, recurring module or onboarding capability. Record the merchant account, environment, processor, currencies, required methods and support owner. Your software should remain the primary order interface; the merchant portal is an operational tool. Map the order and fulfillment flow, including cancellation and delayed fulfillment. Confirm enabled account capabilities and the selected payment environment with Betterpay. Choose sale for immediate authorization and capture, or scope an authorization/capture flow for later fulfillment. Define who reviews uncertain payments, settlement differences and customer support requests.
First milestone: one reconciled sandbox sale
A useful first milestone includes more than a success screen: tokenize a test payment, submit it server-side, persist the gateway ID, inspect the transaction outcome and confirm the record. Then add decline and network-interruption cases before saved cards or wallets. The examples in this portal are source-verified guidance, not evidence that an account has been provisioned or a transaction executed. Do not send private keys or card details through analytics. Use your application ledger to distinguish authorized, paid, refunded and settled states. Keep a record of test evidence and the exact merchant configuration.