Skip to main content
Cresora Commerce
Testing & Sandbox

Certification Scenarios

Required test scenarios you must complete before Cresora issues live API keys.

Complete all required scenarios in the sandbox before submitting for certification. Each scenario tests a critical part of your integration.

🔒Required

All scenarios marked Required must be completed and evidenced before Cresora issues csk_live_ keys.

Card payment scenarios

#ScenarioRequiredTest with
C-01Successful card payment (automatic capture)PAN 4111111111111111
C-02Successful card payment (manual capture)PAN 4111111111111111, capture_method: manual
C-03Card authorization + explicit captureAfter C-02, POST /v1/payments/{id}/capture
C-04Card authorization + voidPOST /v1/payments/{id}/void
C-05Soft decline handlingPAN 4000000000000002
C-06Hard decline handlingPAN 4000000000000069
C-07Full refundPOST /v1/refunds with no amount field
C-08Partial refundPOST /v1/refunds with amount < original

Idempotency scenarios

#ScenarioRequired
I-01Idempotent retry — same result on replay
I-02Idempotency conflict — different params, same key

Webhook scenarios

#ScenarioRequired
W-01Receive and verify payment.captured signature
W-02Handle retry — return 200 on duplicate delivery
W-03Reject stale delivery (timestamp > 5 min)

ACH scenarios (if using ACH)

#ScenarioRequired
A-01Successful ACH debit
A-02R01 return handling
A-03R10 return handling — stop retrying

Error handling scenarios

#ScenarioRequired
E-01401 auth_failed — invalid key
E-02400 validation_error — malformed request
E-03422 processing_error — gateway decline

Submitting certification evidence

Document each scenario with:

  • The API request sent (redact real card numbers)
  • The API response received
  • The webhook event received and verified

Submit your evidence via the Partner Portal under Certification → Submit Evidence, or email it to your Cresora account manager.

See Certification overview → for the full process.