📣 Pinch is now a Fiserv company, find out what that means here.

close
Try Free
Sign In

Key benefits

  • Clean, well-documented REST API

  • Webhooks, sandbox, and staging environments

  • Handles cards, wallets, BECS DD

  • Hands-on implementation support

Pinch is trusted by 3,000+ Aussie businesses

CartonCloud
AiRE
D1g1t
Luna
Scope
Peak

Build Smarter with the Pinch API

This video gives developers a walkthrough of the Pinch API - your gateway to powerful, flexible, and secure payment automation built right here in Australia.

Developer FAQs

Welcome to the Pinch API FAQ. This guide is designed to help developers and technical stakeholders understand the full potential of Pinch's API and developer ecosystem. If you're building payments into your product or service, these questions and answers will help you make the most of what Pinch offers.

What kind of payment infrastructure is Pinch built on?

Pinch operates as a PayFac (Payment Facilitator) and BPSP (Bank Payment Service Provider), which means we offer merchant onboarding, processing, and compliance under a single umbrella. You don’t need to obtain a merchant facility or deal with multiple vendors.

What kind of API does Pinch provide?

Pinch offers a RESTful API that supports key operations such as creating payers, initiating payments, setting up subscriptions, and handling direct debits and cards. The API is clean, versioned, and built for real-world production environments.

Is there a sandbox environment for testing?

Yes! The Pinch sandbox mirrors our production API, so you can build and test your integration without surprises. It even supports "time travel" functionality, allowing you to simulate recurring payments and bank settlement timelines in fast-forward.

Does Pinch provide SDKs or code libraries?

Absolutely. We currently offer an official .NET SDK, complete with NuGet support and usage examples. We also provide a full Postman collection for testing and documentation, including support for environment variables and authentication flows.

How do webhooks work with Pinch?

Pinch supports a range of webhook events so you can subscribe to real-time updates. Events include new payer creation, payment success/failure, direct debit bank result notifications, and subscription lifecycle events.

Can I automate workflows using tools like Zapier or n8n?

Yes. Pinch integrates with popular no-code automation tools like Zapier and n8n. These enable event-driven workflows using our API triggers and actions, such as creating a new payment when a form is submitted or notifying a user of a failed direct debit.

Can I use the API to manage multiple merchants or sub-accounts?

Yes. The API includes functionality for managing multi-merchant setups. This is ideal for platforms acting as aggregators or for marketplaces where each vendor or partner requires their own sub-account for payments.

Our Signature Developer Support

Pinch is built by developers, for developers — and we back that with real support, tools, and guidance. Here's how we support technical teams at every stage:

  • Talk to real devs: Our Aussie engineering team is here to help with questions, edge cases, and integration planning.

  • Free implementation help: We guide you from scoping through to go-live — no guesswork.

  • Clear docs: Easy-to-follow guides and examples for every endpoint and workflow.

  • SDKs & tools: Use our .NET SDK and Postman collection to get up and running fast.

  • Stay updated: Track API changes and improvements with developer-focused release notes.

Real feedback from real developers

"API documentation is good, and the team are amazing to work with. Quick to respond."

Waco M.

"Pinch helped us build a custom flow using their API — backed by a super attentive team."

Andrew E.

"The flexibility and dev support helped us get up and running in days."

Chris G.