Skip to main content
Give the following instruction to your coding agent, such as Codex or Claude Code, in your application project:
The official Prompt, task index and verification checklist are public Markdown files. You do not need a merchant login to read them. You can also copy the instruction from Merchant Dashboard > Developer Tools > API Keys.

​
Choose a path

Your enabled payment channels determine which methods, amounts and currencies are available. New subscription sales are currently paused; this guide covers one-time payments.

​
Prepare access

Create or sign in to your merchant account, check onboarding and payment-channel prerequisites, and obtain credentials in Developer settings. You handle registration, verification, agreement acceptance and payments; the Agent can prepare code and guide you through remaining steps. Set secrets privately in your application’s server environment or secret manager. Do not paste them into Agent conversations or commit them. The native Webhook secret is different from the API key. Configure Webhook before the first native payment, because adding it afterward does not automatically create past order.paid events. There is currently no self-service sandbox key. Use staging only when Kyren supplies its Base URL and matching credentials. Do not use test cards on an unconfirmed live channel.

​
Review the result

Ask the Agent to identify changed files, run local tests and report pending actions. Check signature rejection, duplicate-notification protection, amount/currency association and recovery. Your application must not fulfill purchases from a browser redirect. Local mock tests do not prove a real payment. When you have an authorized test environment, complete its payment step yourself, then verify both the Kyren paid order and your application’s fulfillment record. Review the go-live checklist before production acceptance. Until those steps have been run, the Agent should label them unverified.