Certification
Certification Overview
Why certification exists and how the check run works.
Cresora certification is a structured verification of your integration before production. Cresora is responsible for the behavior of every partner on its platform, so the platform checks integrations directly instead of trusting a description of them.
How it works
Certification is a check catalog run against your sandbox account:
| Check kind | Verified by |
|---|---|
| Automated | The platform, directly against your sandbox activity (payments, refunds, webhook deliveries it observed) |
| Self-attestation | You, in the portal — for obligations only you can confirm (e.g. NACHA authorization display, R10 stop logic) |
| Cresora-ruled | A Cresora reviewer, for judgment calls |
You start the run and re-run checks from Partner Portal → Integration → Certification. There is no evidence-file upload and no email review loop.
What it covers
| Area | Details |
|---|---|
| Technical integration | API correctness, error handling, idempotency, webhook signature verification |
| Payment flows | Hosted-page sale, auth-only + capture, cancel, refund; ACH debit and returns |
| Security | No card data in your logs or requests; correct PCI scope documentation |
| Compliance | NACHA authorization (if ACH), SAQ upload |
Certification vs. sandbox access
| Sandbox | Production | |
|---|---|---|
| Available | Immediately | After certification |
| Requires certification | No | Yes |
| Real money | No | Yes |
Who to contact
Your Cresora account manager owns the relationship; the check run itself lives in the portal under Integration → Certification.