Skip to main content
Status endpoints are always available. For a more reactive experience, also configure a merchant notification URL when your dashboard or integration allows it.

​
Webhook role

A webhook informs your backend when a transaction changes state. It does not replace your status endpoint; it complements it. Your webhook handler should:
  • respond quickly with HTTP 200;
  • be idempotent;
  • store the raw payload;
  • verify the status through the Mysoleas API afterward if the action is sensitive;
  • ignore duplications that were already processed.

​
Recommended merchant-side payload

Depending on the provider and flow, the payload can vary. Structure your processing around stable fields.

​
Defensive verification

After receiving a critical webhook, call the status endpoint.
This verification prevents your system from processing an incomplete payload or a replayed webhook.

​
Expected response

Your webhook endpoint should return 200 as soon as the event has been received.

​
Monetary units in notifications

Transaction and subscription notifications carry major-unit amounts: 4.01 for 4.01 USD/EUR. The core converts the amount before publishing the event. Your receiver must preserve decimals and must not divide this amount by 100 again. Raw provider callbacks retain the provider’s own contract. See amounts and currencies.