Webhooks

Stripe webhooks

Merion uses Stripe for payment processing in the debtor portal. Stripe sends signed webhook events to Merion's internal endpoint; those events drive payment confirmation, balance updates, and case status changes within the platform.

This is a one-way, internal flow — Merion receives events from Stripe. Partners and integrators do not interact with the Stripe webhook endpoint directly. If you are building a payment integration on behalf of a client, contact Merion to understand how payment events propagate to the partner API.

How payment events work

1. A debtor completes payment in the Merion debtor portal.
2. Stripe fires a payment_intent.succeeded (or equivalent) event to Merion's webhook endpoint.
3. Merion validates the Stripe signature and processes the event.
4. The relevant case record is updated in the platform (payment received, balance adjusted).
5. The client's portal view reflects the update in near-real-time.

The Stripe webhook endpoint is not publicly documented because partners and integrators do not post to it. If you need to query payment status programmatically, use the authenticated partner API (requires approval — see Getting Started).

Partner webhooks (roadmap)

Outbound partner webhooks — where Merion pushes case status change events to a URL you register — are on the roadmap. They are not available as a general product at this time.

If you have a specific requirement for event-driven integration (e.g., you want to receive a push when a debt is collected or a case is closed), contact Merion at [email protected]. Arrangements can be made for individual approved partners on a case-by-case basis while the general product is in development.

Polling as an alternative

Until partner webhooks are generally available, approved integrators can poll the authenticated partner API for case status changes. The recommended approach is a low-frequency poll (every few minutes, not seconds) with cursor-based pagination on the updated_since parameter to retrieve only changed records.

Aggressive polling will trigger rate limiting. See the Getting Started page for rate limit guidance.

Questions

If you have questions about event-driven integration not covered here, email [email protected] or visit the Status & Support page.