Integrating Tokens into Your Skyfire Services
Three ways to require and validate Skyfire tokens in your seller service, from the simplest header check to full account provisioning.
Each buyer agent that calls your seller service includes a Skyfire token with its request.
Skyfire tokens are standard signed JWTs. When a request reaches your service, it should include a token in the
kyapay-tokenheader.Older integrations may use the
skyfire-pay-idheader, but this is deprecated and being replaced.
Pass tokens in that dedicated header rather than the standard Authorization header. Many services already use Authorization for their own authentication, and reusing it for kya, pay, and/or kya-pay tokens can cause conflicts or unintended behavior.
Choose one of three integration paths below, depending on the level of control and security your service needs.
Recommended. Require the agent to include a token (kya, pay, and/or kya-pay) with each request, in the kyapay-token header.
Your service validates the token to authorize the agent, and may support charging flows tied to pay or kya-pay tokens. This is the simplest and most common integration pattern.
Other integration paths may be possible. Contact [email protected] to discuss your specific use case.
Updated 16 days ago