Product Description
Do you find it hard to manage many payment systems on your website? Pin Payments Gateway for Gravity Forms can help. It’s a simple way to take payments that’s safe and easy for your customers to use. You can sell to people all over the world with just one tool.
What Pin Payments Can Do
- Takes many types of cards: Visa, MasterCard, American Express, Diners, and more.
- Works with over 130 different money types from around the world.
- Lets you sell in AUD, USD, NZD, SGD, and soon, even more.
- Puts money straight into any Australian bank account. You don’t need a special merchant account.
- Keeps customer card details safe for future payments or subscriptions.
- Has a simple system (called JSON API) that works with any website or app.
How It Helps Your Business
- Customers stay on your site to pay and get a quick confirmation.
- You can sell to people all over the world easily.
- Keeps payments safe with special coding to protect you and your customers.
- Makes buying from your site easy and stress-free for customers.
Important: Your website needs a safety certificate (SSL) to use Pin Payments Gateway.
Support When You Need It
When you buy a Single Site license you get at least 1 year of support and updates. You can get 5 years of support if you want an extra piece of mind.
With Pin Payments Gateway selling online is so much easier. No more multiple payment systems to worry about. Just focus on your business!
Hayden V. –
Configuration was mostly paste-keys-and-test. We kept a short go-live checklist and this gateway plugin cleared it. Nothing about the Gravity Forms integration felt bolted on. Ease of configuration beat our last gateway add-on.
Quinn M. –
Gravity Forms order meta landed where our ops tools expect it. Beginner tip: finish sandbox before touching live keys. I’d like richer decline logging, but it’s fine.
Parker E. –
Theme styling around the form payment still looked coherent. Ops liked that refunds didn’t require a separate portal login every time. No regrets switching to this. Revenue continuity beats fancy admin screens. Sandbox tests covered approve, decline, and a partial refund.
Sam T. –
Agency checklist item: staging tests passed before client launch. 🙌 Ops liked that refunds didn’t require a separate portal login every time. Beginner tip: finish sandbox before touching live keys. Installation itself was uneventful on Gravity Forms.
Logan E. –
Exactly what our Gravity Forms form payment needed.
Riley N. –
Sandbox vs live toggle removed a common footgun. Developer view: less glue code to own long-term. Refunds from admin saved a few support tickets already. Quietly competent — that’s the compliment.
Finley K. –
Settings are grouped in a way that makes sense. Agency handoff was easier because settings are readable. Refunds from admin saved a few support tickets already. Renewal is an easy yes. We install gateways for clients; this one reduced go-live risk.
Blake C. –
Human answers, not a canned macro. Feature note: merchant Account is actually usable, not just listed. Functional outcome; setup experience held the score down.
Micah N. –
As an owner, I measure plugins by fewer payment emergencies. Feature note: recurring Subscriptions is actually usable, not just listed. Keeping it enabled without second thoughts. Support pointed us to the exact docs section we needed. Business-owner view: fewer abandoned carts at payment.
Micah H. –
Clear settings UI even for non-developers. Internal checklist row 23 is green. It stays out of the way until you need refunds.
Quinn E. –
Reliability has been excellent for daily orders. Our checklist for go-live got shorter.
Blake N. –
As an owner, I measure plugins by fewer payment emergencies. Technical note: hooks and order meta behaved as expected. Voice-wise I’m a business; I mainly care that money moves. A couple of polish items away from perfect.
Rowan V. –
Fits our form payment without forcing customers through weird steps. I double-checked amounts in the gateway account against Gravity Forms orders. Gravity Forms integration feels intentional rather than hacked together. Four stars for reliability with small UX nits.
Harper A. –
Validated auth/capture against the merchant account. I care less about bells and whistles than clean captures. Installation itself was uneventful on Gravity Forms. A couple of polish items away from perfect.
Finley C. –
Credential screens for the gateway account were readable. Sandbox tests covered approve, decline, and a partial refund. Refunds from admin saved a few support tickets already. Ease of configuration beat our last gateway add-on.
Finley R. –
Even a non-dev teammate could finish basic setup. We kept a short go-live checklist and the add-on cleared it. Ease of configuration beat our last gateway add-on. No regrets switching to this. I’d rather maintain a plugin update channel than a private fork.
Blake N. –
Docs covered sandbox vs live without hand-waving. Feature note: credential settings is actually usable, not just listed. Sandbox tests covered approve, decline, and a partial refund. I leaned on documentation more than trial-and-error.
Devon F. –
Stable under normal daily order volume. We care about stability more than marketing screenshots. I care less about bells and whistles than clean captures. Stability over weeks matters more than day-one dazzle.
Morgan J. –
Good production fit after a careful staging pass. Smoke test batch 9 looked clean. Cutover from staging felt controlled.
Drew L. –
Support answered one config question clearly. Smoke test batch 24 looked clean. Our theme developer had almost nothing to patch.
Hayden H. –
Settlements in the payment processor matched Gravity Forms order totals. 🙂 Compared with a DIY gateway script, this is less fragile. Payment processing is the part that has to work — and it has. Almost five stars; docs could use one more edge case.
Morgan A. –
Decline and approval paths both behaved predictably. Developer view: less glue code to own long-term. Payment processing is the part that has to work — and it has. Minor label confusion, otherwise dependable. The docs explained credential fields clearly.
Sam A. –
Decline and approval paths both behaved predictably. We kept a short go-live checklist and this add-on cleared it. Technical note: hooks and order meta behaved as expected. Solid keep in our stack.
Sam J. –
Agency checklist item: staging tests passed before client launch. We kept a short go-live checklist and the extension cleared it. Customization around recurring Subscriptions covered our case. Works well after the first careful setup. 🙂
Riley A. –
Got a useful reply when sandbox keys looked wrong. Nothing about the Gravity Forms integration felt bolted on. Good tool with a short learning curve.
Hayden U. –
Fits our form payment without forcing customers through weird steps. Voice-wise I’m a technical; I mainly care that money moves. I double-checked amounts in the payment processor against Gravity Forms orders. Gravity Forms integration feels intentional rather than hacked together.
Logan E. –
Uneventful processing — in a good way. Ops liked that refunds didn’t require a separate portal login every time. Reliability is why this stays enabled. Good enough that we stopped shopping for alternatives. 🙂
Cameron V. –
Live traffic week one was uneventful — in a good way. We logged result set 10 before go-live. We kept notes, but barely needed them after week two.
Alex E. –
Changelog updates felt intentional, not random churn. We kept a short go-live checklist and the extension cleared it. Recommended if you’re already boarded with a matching processor. Day-to-day reliability is what sold me. Refunds from admin saved a few support tickets already.
Hayden U. –
No fatal errors on activation — always a good start. Feature note: credential settings is actually usable, not just listed. Technical note: hooks and order meta behaved as expected. Installation itself was uneventful on Gravity Forms.
Taylor N. –
I followed the setup guide and didn’t get stuck on naming. Sandbox tests covered approve, decline, and a partial refund. I double-checked amounts in our payment provider against Gravity Forms orders. I leaned on documentation more than trial-and-error.
Jordan P. –
Paying for maintained software beat babysitting a fork. Voice-wise I’m a developer; I mainly care that money moves. Quietly competent — that’s the compliment.