Skip to content
Pinch Payments logoPaddle logo

Connect Pinch Payments to Paddle

Move data between Pinch Payments and Paddle 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.

Pinch Payments triggers
14
Pinch Payments actions
8
Paddle triggers
5
Paddle actions
6

Automation ideas

What you can build with Pinch Payments and Paddle

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

  • Bank Results Event in Pinch Payments creates List Customers in Paddle

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

  • New Active Subscription in Paddle creates Create or Update Payer in Pinch Payments

    Triggers when a subscription activates — a trial converts or the first payment succeeds.

  • Bank Results Event in Pinch Payments creates Get Subscription in Paddle

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

  • New Active Subscription in Paddle creates Create Realtime Payment in Pinch Payments

    Triggers when a subscription activates — a trial converts or the first payment succeeds.

  • Bank Results Event in Pinch Payments creates Update Subscription in Paddle

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

  • New Active Subscription in Paddle creates Add Source to Payer in Pinch Payments

    Triggers when a subscription activates — a trial converts or the first payment succeeds.

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 Pinch Payments and acts in Paddle, 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.