Developers · APIs & Integration
Build Payments on Infrastructure That Answers
Documented APIs, sandbox access, hosted components, tokenization workflows, and webhooks — so your team can build payment experiences while keeping underwriting, risk, and operational reporting in view.
Integration Surface
The Building Blocks You Integrate
Choose the integration depth that fits: full API control, hosted components that reduce sensitive-data handling, or a mix of both.
Documented APIs
Developer documentation and integration guidance at apidocs.cliq.com. Exact endpoints, authentication, and event behavior are confirmed in the current docs.
Sandbox Access
Build and test integrations in a sandbox environment before anything touches production, for eligible implementations.
Webhook Events
Notify your platform when payment, refund, dispute, or status changes occur where events are available.
Hosted Components
Use hosted pages or payment components where a full custom checkout is unnecessary.
Tokenization Workflows
Support tokenized payment data and card-on-file use cases where configured and approved.
Reporting & Exports
Keep gateway and payment activity connected to transaction, settlement, dispute, and reconciliation reporting.
How It Works
From First Docs Read to Production Launch
Integration works best when the approved use case is defined before the first API call.
- ScopeDefine the payment flows, channels, risk considerations, and reporting needs for the approved use case
- Build in SandboxDevelop against sandbox credentials with hosted pages, gateway workflows, APIs, and webhooks per the docs
- IntegrateConnect payment activity to your software, dashboards, accounting, and support systems where appropriate
- LaunchMove to production with monitoring, webhooks, and reporting keeping operations and developers in sync
Security-Minded Integration
Build Without Carrying the Sensitive Data
The fastest way to a secure integration is to never touch raw card data in the first place.
- Hosted fields and pages can reduce direct sensitive-data handling compared with custom forms
- Tokenization and hosted workflows support card-on-file use cases where configured and approved
- Webhook events help developers and operators respond to payment-state changes
- Hosted workflows can reduce sensitive-data handling, but PCI responsibilities depend on implementation and business practices
Who It's For
Developer workflows matter for teams that need integration flexibility and payment visibility.
Developers
Developer Teams
Use docs, hosted pages, gateways, and webhooks to build payment experiences with operational context.
ISV
ISVs & Platforms
Embed payment acceptance while keeping merchant onboarding, webhooks, and reporting in view.
Ecommerce
Ecommerce & Digital Checkout
Connect online checkout, payment pages, tokens, and reporting to approved processor configurations.
The Essentials
Frequently Asked
Do developers get API documentation?
Cliq provides developer documentation and integration guidance at apidocs.cliq.com. Exact endpoints, authentication, and event behavior are confirmed in the current docs.
Is there a sandbox environment?
Yes. Documented APIs and sandbox access support embedded payment workflows for eligible implementations, so teams can build and test before production.
Do developers get webhooks?
Webhook or event workflows may be available to notify connected systems about payment-state changes, depending on integration and configuration.
Do hosted components reduce PCI scope?
Gateway and hosted payment workflows can reduce sensitive-data handling, but PCI responsibilities depend on implementation and business practices — see Hosted Payment Pages.
Start in the Sandbox Today
Read the docs, scope your integration, and tell Cliq which flows, events, and systems your build needs to support.
Or call us directly at (866) 634-3044