Skip to content
Chargebee logoPinch Payments logo

Connect Chargebee to Pinch Payments

Move data between Chargebee and Pinch Payments the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Chargebee triggers
8
Chargebee actions
5
Pinch Payments triggers
14
Pinch Payments actions
8

Automation ideas

What you can build with Chargebee and Pinch Payments

A few flows teams run between Chargebee and Pinch Payments. Use one as a starting point, or build your own from scratch.

  • Subscription Created in Chargebee creates Create or Update Payer in Pinch Payments

    Triggers when a new subscription is created for a customer.

  • Bank Results Event in Pinch Payments creates Create Subscription in Chargebee

    Triggers when a bank account transaction returns (may result in dishonour status)

  • Subscription Created in Chargebee creates Create Realtime Payment in Pinch Payments

    Triggers when a new subscription is created for a customer.

  • Bank Results Event in Pinch Payments creates Cancel Subscription in Chargebee

    Triggers when a bank account transaction returns (may result in dishonour status)

  • Subscription Created in Chargebee creates Add Source to Payer in Pinch Payments

    Triggers when a new subscription is created for a customer.

  • Bank Results Event in Pinch Payments creates Create Customer in Chargebee

    Triggers when a bank account transaction returns (may result in dishonour status)

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Chargebee and acts in Pinch Payments, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.