Yes. You can continue using your Swagger or OpenAPI definitions and align request/response models with Cruisepay endpoints for payment, status, and refund flows.
Yes. Use sandbox API keys and callback URLs to validate authorization, 3DS redirects, and final transaction states before going live.
Call the transaction status API using the merchant invoice number and store both callback and status responses for reconciliation.
Confirm transaction eligibility, refund amount limits, token permissions, and the callback endpoint handling for pending, success, and declined outcomes.
Use idempotent invoice numbers, client-side timeouts, and controlled retries with exponential backoff to prevent duplicate charges and improve resilience.
Yes. Allowlist Cruisepay API domains and callback source IPs in your firewall policies, then validate outbound HTTPS access from your application servers.
Share invoice number, transaction ID, timestamp, environment, callback logs, and the exact request payload (excluding sensitive card data).
Secure payment processing APIs for seamless checkout and refunds. API Version: v1