Stripe + StackGo

Run compliance from inside Stripe. Checks start from a record and the result lands back on the client.

Stripe publishes 16 trigger events and 13 actions on its public Zapier listing. That is what a StackGo connector would be built on.

Accounting System of record Not connected yet
What Stripe is

Stripe is a developer-friendly way to accept payments online and in mobile apps. Stripe's suite of APIs powers commerce for thousands of companies of all sizes, processing billions of dollars for businesses each year.

Description supplied by Stripe.

The trigger

What starts a check

You do not open StackGo. A change in the system starts the work, and the system stays your source of truth.

  • New Customer
The write-back

What StackGo puts back on the record

A Stripe connector would write the outcome, the status and a link to the result onto the record by default. These are the fields StackGo can write on the systems it connects to today.

  • Verification status
  • Risk rating
  • Last checked
  • Report link
  • Verified name
  • Date of birth
  • Document checked
  • Screening result
  • Beneficial owners
  • Form responses
  • Verification report (PDF)

Personal fields are off by default. What goes back to your CRM explains the default; what each field holds is set out in what “integrates with” actually means.

How it lands in Stripe
  • Create Customer

Stripe's own write operations. The result goes onto the record you already work in.

Everything else Stripe publishes

Stripe’s public integration surface

The rest of what Stripe exposes on Zapier, beyond the ones above. This is the raw material a connector would use.

15 more events
  • Canceled Subscription
  • Checkout Session Completed
  • Failed Payment
  • Invoice Payment Failed
  • New Charge
  • New Dispute
  • New Subscription
  • New Event
  • New Invoice Item
  • New Invoice
  • New Payment
  • New Payment Link
  • New Refund
  • Updated Subscription
  • Updated Dispute
12 more actions
  • Cancel Subscription
  • Confirm Payment
  • Create Checkout Session
  • Create Invoice
  • Create Payment
  • Create Payment Link
  • Create Price
  • Create Product
  • Create Subscription
  • Deactivate Payment Link
  • Update Customer
  • API Request (Beta)

Names are Stripe’s own, read from its public Zapier listing on 23 October 2026.

Questions

Common questions about Stripe

What is Stripe integration?

There is no StackGo connector for Stripe yet. Stripe publishes 16 trigger events and 13 actions through Zapier, including “New Customer”, so building one is realistic. Requests decide the build order.

How would a check result show up in Stripe?

Through Stripe’s own write operations: “Create Customer”. You choose which fields are written, and you can also run it one-way, with nothing written back to Stripe at all.

Questions taken from what people actually search in Australia. We answer only the ones our own data answers.

Where this sits

Stripe is the record. StackGo runs the steps around it.

Every step writes back to Stripe, so the client record stays the source of truth.

Want Stripe connected?

Requests decide the build order. Tell us and we will tell you where it sits.

Request this integration

Ready to make onboarding minutes, not hours?

Start free and run your first check today, or book a demo and we will walk you through it.

Cookie settings

Choose which optional cookies we can use. You can change this at any time from Cookie settings at the bottom of every page.