Developer notifications
There is currently no single accepted developer webhook contract for signatures, delivery and retries. This page therefore does not invent subscription instructions, signature headers, retry windows or delivery guarantees.
Handle model responses using the API reference, and inspect uncertain outcomes in My requests. Long-running compliance operations use their documented operation/provider status queries.
Payment callbacks are separate
Integrated payment channels verify their own signatures and payment facts. A browser redirect only associates an order; clients cannot declare successful payment. Continue querying an already paid order that awaits fulfillment rather than purchasing again.
Any future notification API needs published event types, verification, retries, idempotency and recovery before a working integration tutorial can be provided. Use the documented query/response flows today.