Events
Events allow your platform to stay synchronized with connected accounts as their state changes over time.
They are a critical part of any Connect integration.
Why events matter
Not all account changes happen synchronously with an API request.
For example:
- submitted information may enter review
- verification may complete asynchronously
- a previously operational account may become restricted
- capabilities may change after re-evaluation
Your platform should use events to detect and respond to these changes.
A successful API response confirms that data was accepted. It does not guarantee that the account is fully verified or operational.
What events are used for
In a platform-managed onboarding flow, events are commonly used to:
- detect account state changes
- re-evaluate requirements
- update user-facing onboarding status
- trigger requests for additional information
- monitor capability activation
Event-driven model
A typical pattern looks like this:
Your platform creates or updates the account.
Paypercut sends an event when account state changes.
Your platform retrieves the latest account object.
Your platform updates UI, workflows, or operational logic.
Webhooks
Events are delivered through webhooks.
Use webhooks to receive notifications when account data, requirements, or capabilities change.
See:
Recommended approach
Your platform should treat events as part of the core integration flow.
In practice, this means:
- subscribing to relevant events
- processing them idempotently
- re-fetching the affected resource
- driving platform state from the latest API response
Key principle
Use API responses to confirm writes.
Use events to detect state transitions.
