Readiness Preflight
Run these in order. Never print a secret: report lengths and yes or no only.
Credentials are set. The secret file exists and is excluded from git. Report
set (N characters)oremptyfor each credential, and flag a key equal to the secret, whitespace in a value, placeholder text, or a percent sign in a fee setting.Config loads with the project's own loader. A validation message is safe to show.
Credentials work, with one read-only call:
Role Call Expect Partner get-sellerswithpayme_client_keyandpage_size: 5status_code0Direct seller get-transactionswithseller_payme_idandpage_size: 1status_code0Error 200 or error 251 here usually means a value from the wrong environment.
The server is running the current settings. Compare the process start time with the settings file's modified time. The startup log should show the callback address it will send, and not
localhostonce a tunnel exists.The public address answers from the internet. If you have no public address yet, start a tunnel with
cloudflared tunnel --url http://localhost:<port>, following the recipe, with Windows steps. PayMe hasn't run that recipe end to end. Call your health route through the address, such as<public address>/health:Result Meaning 200 Good 502 The tunnel is up and your server is down Cloudflare error 1033 The tunnel process has gone. A quick tunnel's address goes with it You can call your own endpoints. The person creates an admin credential for your app, so you never see it. For your own runs, keep a temporary one in a shell variable, never echo it, and revoke it when done.
PayMe's side is confirmed: a terminal is connected, and for partners the Default Callback URL is set. See What to Ask PayMe First.
Downloading a binary or opening a public tunnel is often blocked for an agent. Give the person the recipe's exact commands, ask them to paste back only the public address, which isn't a secret, and update the settings for them.
Next: Sandbox Walk-through.