Support

OID4Pay is a small team. The paths below are the support channels for the public beta.

File a bug

• Open an issue at https://github.com/oid4pay/oid4pay/issues.
• Include a reproducer (curl invocation, code snippet, or screenshot).
• Specify which host the bug applies to (sandbox vs production).
• Tag with bug, docs, or sdk:+language.

Request a production API token

Production access requires:

1. A merchant of record signed and accepted on the directory at discover.oid4pay.com.
2. The standard merchant agreement signed (linked to from the merchant onboarding flow).
3. A registered private_key_jwt public key in the merchant's JWKS.

Email onboarding@oid4pay.com with your merchant ID after sandbox testing completes. Onboarding SLA: 5 working days.

Security disclosure

Coordinated security disclosure goes through the RFC 9116 channel documented at /security and /.well-known/security.txt. Acknowledgment within 24 h; triage within 5 working days.

Integration help

For non-bug integration questions, the fastest paths are:

• The merchant quickstart and agent quickstart.
• The wire reference and the per-mechanism protocol pages.
• GitHub Discussions at https://github.com/oid4pay/oid4pay/discussions.
• Email developers@oid4pay.com for paid-tier integrators (response within 1 working day).

Status and incident communication

Subscribe to Statuspage at oid4pay.statuspage.io. Critical-incident postmortems land on incident history.

Languages

Default support is English. Dutch, German, and French are honoured on best-effort basis (matching the Preferred-Languages entry in security.txt).

What is out of scope

• Building your storefront UI (use the CDN bundle or the merchant SDK).
• Stripe Connect account management (talk to Stripe; we cannot mediate).