How you integrate with PayNimble

Gateway integrations are built on the NMI platform. Merchants and their developers can integrate at whatever depth the project requires — from a fully hosted page that keeps the merchant environment out of PCI scope, to a direct server-to-server API for embedded checkout and back-office automation.

• Direct Post API — server-to-server sale, auth, capture, refund, void, and credit
• Three-Step Redirect API — embedded checkout that keeps card data off your servers
• Collect.js — drop-in tokenization for custom front-end checkout experiences
• Customer Vault — store and reuse payment credentials for recurring and card-on-file
• Network tokenization and account updater on supported card brands
• Query API and webhooks for reporting, reconciliation, and event-driven workflows
• Recurring / subscription billing plans managed at the gateway layer
• Semi-integrated card-present flows to the same gateway account

CAMPPS is our Customer Account Management & Payment Processing Solution for billers. Integration is typically account-file based rather than transaction-API based: you supply an account/balance file, customers pay through the channels we host, and we return a posting file (or real-time notification) that your billing system consumes.

• Scheduled account-file exchange (SFTP) for balance and account lookup
• Posting-file returns in your billing system's expected format
• Hosted EBPP portal, IVR, agent-assisted, Text2Pay, and autopay channels
• Real-time payment notification available where your platform supports it
• Service-fee and convenience-fee programs configured per channel
• ACH origination and card acceptance under a single remittance view
• e-signature capture tied to enrollment and payment-plan workflows

Card-present deployments run standalone or semi-integrated. Semi-integrated is the default recommendation: your application never touches cardholder data — it hands the amount to the terminal and receives a result — which keeps the point-of-sale environment out of PCI scope.

• Semi-integrated terminal flows through the PayNimble Gateway
• EMV chip, contactless, and mobile wallet acceptance
• Clover developer platform for app-level POS integrations
• Terminal estate management, key injection, and lifecycle support

Authorization and settlement run through our acquiring partners. Funding settles to the DDA you already use — there is no requirement to change banking relationships as part of an integration.

• Interchange-plus card pricing and per-item ACH pricing
• Settlement and funding reporting available through the gateway
• Chargeback and dispute workflow support