Payment integrations

    Your payment provider. Your revenue.

    Connect charging sessions to the payment provider that fits your business. Use a ready-made JPlug connection, request a regional provider, or build your own integration with our APIs.

    No provider lock-inRegional payment supportCustom API pathway

    Your payment stack

    One charging platform. Your choice of provider.

    Stripe logo
    IDBank logo
    Mercado Pago logo
    Monex logo

    Your provider

    Connect with JPlug APIs + webhooks

    Payment connections

    Bring the provider you already trust.

    Start with an existing connection or use JPlug’s open integration path when your market calls for something different.

    Stripe logo

    Stripe

    Global

    Ready to connect

    Connect your Stripe account to collect charging payments through a familiar global platform.

    IDBank logo

    IDBank

    Armenia

    Ready to connect

    Power local payment experiences for charging networks operating in Armenia.

    Mercado Pago logo

    Mercado Pago

    Latin America

    Available on request

    Bring a locally recognized payment experience to drivers across Latin American markets.

    Monex logo

    Monex

    Mexico

    Ready to connect

    Use your existing Monex relationship for payment flows tailored to your deployment.

    { JPlug API }

    Custom API integration

    Any supported market

    Ready to use

    Connect another API-enabled provider while JPlug keeps charging sessions and payment results in sync.

    Need another?

    Your provider can be next.

    Tell us which processor your business uses. We’ll help you choose the fastest path to a working connection.

    Discuss your provider

    Provider availability and supported capabilities can vary by country, account, currency, and payment flow.

    Payment freedom

    Your choice stays yours.

    Your payment strategy should match your market—not the limitations of your charging software.

    Keep your provider relationship

    Use the processor account, commercial terms, and settlement arrangement that already work for your business.

    Serve every market locally

    Choose regional providers and payment experiences that your drivers already know and trust.

    Change without starting over

    Your charging operations stay on JPlug as your payment strategy evolves across markets and providers.

    Stay in control

    Decide which provider handles your payments instead of being forced into a platform-owned gateway.

    How it works

    From provider to payment in three steps.

    0101

    Choose your connection

    Start with a ready-to-connect provider, request an available integration, or bring an API-enabled provider of your own.

    0202

    Connect and configure

    Link your provider account and configure the checkout, currency, pricing, and payment flow for your network.

    0303

    Launch on JPlug

    Drivers pay through your selected provider while JPlug connects each payment result to the right charging session.

    Open integration path

    If we don’t have it, build it.

    Connect another API-enabled processor while JPlug continues to manage chargers, sessions, tariffs, and energy data. Your integration handles provider-specific logic; JPlug keeps the charging experience connected.

    Webhooks and real-time events
    Payment status synchronization
    Secure server-side integration
    Provider-specific payment logic
    Read the API documentation
    payment-flow

    01 session.completed

    02 → send amount to your provider

    03 ← receive payment result

    04 payment.confirmed

    Charging session synchronized

    Keep provider credentials in your secure server environment.

    Common questions

    Payment integrations, explained.

    Availability depends on the provider account, market, and payment flow. We’ll confirm the details before launch.

    What does “Ready to connect” mean?

    JPlug already has an integration path for that provider. Our team will help you connect credentials, configure the payment flow, and validate the setup before it goes live.

    What does “Available on request” mean?

    The provider can be enabled for qualifying deployments, but it is not a self-serve connection yet. Contact us so we can confirm the market, account requirements, and implementation timeline.

    Can we use a payment provider that is not listed?

    Yes. If the provider exposes the APIs, authentication, and payment events required by your deployment, your team can connect it using JPlug APIs and webhooks. We can also help evaluate the integration.

    Who manages our payment-provider account and fees?

    When you bring your own provider, you keep your direct account and commercial agreement with that provider. Its processing fees and settlement terms remain separate from your JPlug subscription.

    Bring your payments. We’ll bring the charging platform.

    Tell us where you operate and which provider you use. We’ll help you map the right connection path.

    All provider names and logos are trademarks of their respective owners.