Migration Guide

This guide covers the key differences to account for when migrating from another payment processor to Cresora.

Key differences from common gateways

API key format

Cresora uses csk_test_ / csk_live_ prefixes. Update all references in your codebase — do a project-wide search for your old key format and replace every occurrence.

Single host, key-selected environment

There is no separate sandbox URL. Replace your gateway's sandbox.api.example.com with api.cresoracommerce.com and switch the key to csk_test_.

Idempotency keys

If your previous gateway didn't require idempotency keys, add them now. Every POST /v1/payments and POST /v1/refunds should include a unique Idempotency-Key header.

Amount format

Cresora uses minor units (cents). If your previous gateway used decimal amounts (100.00), update your amount math. See Amounts & Currency →.

Webhook signature

Cresora uses HMAC-SHA256 signed with your endpoint's signing secret. Remove your old gateway's webhook verification and implement the Cresora version — see Signature verification →.

Migration checklist

• Update API keys throughout codebase
• Update API base URL to https://api.cresoracommerce.com
• Add Idempotency-Key to all POST requests
• Update amount handling to minor units
• Update webhook signature verification
• Re-register webhook endpoints in the Partner Portal
• Update error code handling to Cresora error codes
• Re-run certification scenarios in the sandbox
• Update test card numbers to Cresora test PANs

Cresora test PANs

Replace your old gateway's test cards with Cresora's:

See Testing & Sandbox → for the full list.

Support during migration

For migration support, contact Cresora developer support via the Support page → or open a ticket in the Partner Portal. Include your previous gateway name and we'll provide a tailored migration guide.