Build against a documented contract.
Start with live Credia Payments documentation or request access to the Private Beta developer paths for Identity, Auth, Verify, Reputation and Proof-of-Actor. Each guide identifies the actual supported contract, environment and version.
Payment documentation.
Review payment setup, supported environments, API authentication, idempotency and webhook handling.
Application-side Proof-of-Actor integrations.
Credia Proof-of-Actor serves the application receiving interactions. Discuss the supported web, mobile or API environment, the evidence available and observation-mode evaluation. Existing payment SDK examples do not establish Proof-of-Actor support.
Integrations with explicit support levels.
A package, an example recipe and a roadmap idea are different things. Each integration page names its artifact or recipe, tested version, product scope and limitations.
Private Beta developer access.
Identity, Auth, Verify, Reputation and Proof-of-Actor share their developer documentation with beta teams during onboarding.
Moving from Proof of Actor?
Proof of Actor is becoming Credia Proof-of-Actor. Review the migration guide before changing any existing integration.
Start building with Credia Payments.
Create an agent wallet, grab an API key and make your first payment request.