Payment lifecycle
Payment Callbacks and Webhooks
Understand how provider callbacks complete SparkGlim transactions and what your integration can rely on.
Provider callbacks belong to the payment configuration
SparkGlim verifies configured provider callbacks before processing payment results. The callback handlers are part of the payment infrastructure; they are not general public event-subscription endpoints for an external application.
Do not infer an outbound subscription API
The public API registry does not define a generic webhook subscription contract. If your deployment requires outbound event delivery, agree the enabled events, destination, signature format and retry behavior with SparkGlim before implementing a receiver.
Keep fulfillment tied to transaction state
Store the reference returned by payment initialization and use the supported verification flow to resolve pending results. Browser return URLs are navigation, not proof of payment, and retries must not create duplicate fulfillment.