Stripe + StackGo
Run compliance from inside Stripe. Checks start from a record and the result lands back on the client.
Stripe publishes 4 trigger events and 16 actions on its public Zapier listing. That is what a StackGo connector would be built on.
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.
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.
| Event | What StackGo does | What comes back |
|---|---|---|
| A new contact or customer is created | Starts identity collection | Verification status |
| A designated service is added | Runs the checks that service requires | Result and risk rating |
| Ownership or details change | Re-screens the related parties | Updated status |
What StackGo puts back on the record
A Stripe connector would write named fields onto the record, not a link to a portal. These are the fields StackGo writes 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)
Every field is optional. What each one holds, and which carry personal data, is set out once in what “integrates with” actually means.
- Create Customer
Stripe's own write operations. The result goes onto the record you already work in.
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.
- Canceled Subscription
- Checkout Session Completed
- Failed Payment
- Invoice Payment Failed
- 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
- Custom Actions (Beta)
- API Request (Beta)
- Find Account Balance
- Find Account by ID
Names are Stripe’s own, read from its public Zapier listing on 28 August 2026.
Common questions about Stripe
What is Stripe integration?
There is no StackGo connector for Stripe yet. Stripe publishes 4 trigger events and 16 actions through Zapier, 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.
Stripe is made by stripe.com. We are not affiliated with them.
Want Stripe connected?
Requests decide the build order. Tell us and we will tell you where it sits.
Request this integrationReady 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.