SparkGlim Developer
Hand off to SparkGlim Checkout.
Connect the supported checkout session and return path. SparkGlim Server retains payment pricing, provider selection, verification and fulfillment.
Build the request
Create the supported session through the appropriate API using the actual campaign, ticket or nominee context and required customer fields. The server validates quantities, amounts and available payment configuration.
Continue through checkout
Open the returned checkout.sparkglim.net URL. Let checkout present its available payment methods; normal request pages do not choose a provider or initialize a second payment.
Payment ownership
SparkGlim Server processes the authoritative result and fulfillment. The public frontend only hands off and receives the configured return; it must not verify, poll or infer payment from navigation.
Retries and idempotency
Retain the same business reference and idempotency key for a retry. Country or language selection does not change selling currency, activate providers or override campaign payment eligibility.