Integration checklist¶
Go live only when every item below holds in SANDBOX; then repeat the last two with x-env: PROD and production credentials.
What Payard provides¶
| Item | Notes |
|---|---|
| API host | For each environment |
| Merchant account and licence | SANDBOX first, PROD later |
| Merchant application id and secret | Or create the application in the dashboard |
| Confirmed IP allow-list | Send Payard your public egress IPs |
| Provider bindings | Providers, payment systems, currencies, countries and redirect URLs agreed with you |
| Webhook public key (PEM) | For each environment |
What you build¶
- Request signing that matches both test vectors in Authentication.
- API keys of the lowest type each system needs, secrets kept server-side.
- A fresh
idempotencyKeyper payin, payout and refund, stored before the call and reused on retry. - Amounts sent as integers in minor units.
- A webhook endpoint on public HTTPS that verifies the RSA signature over the raw body, answers
2xxwithin 20 seconds and processes asynchronously. - Webhook handling that re-reads the entity, tolerates duplicates and any order, and ignores
"test": truedeliveries. - A reconciliation job that polls non-final transactions and payouts through
get-all. - Error handling that branches on
errorCodeand treats a timeout as "unknown", not "failed". - One payin and one payout tested end to end in
SANDBOX, including the webhook.
Support¶
For credentials, IP registration, provider setup and incidents, contact your Payard account manager. Quote the transaction or payout id or code and the request path and timestamp from any error.