KreedX — Banking API and Payments Platformby DigiPulse Solutions
Developer Docs
General guide

Conventions

How every API here behaves.

These hold across the catalogue, so once you have integrated one API the next one is familiar.

StyleREST over HTTPS, with predictable JSON responses
EnvironmentsSandbox and production, with separate credentials for each
Asynchronous eventsWebhooks to an HTTPS endpoint you provide
Every transactionCarries a unique reference ID, through to settlement
FailuresRetried where the network allows, then returned as a clear status rather than left pending
ToolingSDK samples and code examples, shared during integration
AvailabilityEnterprise-grade uptime SLA

The details behind these — how errors look, and how to learn a transaction's final result — are in Status & Error Codes and Webhooks & Transaction Status.