Cellpoint Digital API
Cellpoint's Velocity platform has a documented public payments API over HTTPS with XML bodies, plus iOS and Android SDKs and a hosted payment page. Access is not self-serve: credentials arrive only after a commercial agreement, and there is no public sandbox.
Frequently asked questions
Cellpoint Digital scores C on the API Report Card. Cellpoint's Velocity platform has a documented public payments API over HTTPS with XML bodies, plus iOS and Android SDKs and a hosted payment page. Access is not self-serve: credentials arrive only after a commercial agreement, and there is no public sandbox.
Cellpoint Digital has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood.
CellPoint Digital is a payment orchestration platform (POP) purpose-built for the global travel industry, airlines, OTAs, hospitality groups and travel retailers.
Vertical: Financial Services (payment orchestration), with a deep vertical focus on travel and airline retailing. Multi-acquirer payment routing: Route a single card / wallet / APM transaction across 220+ PSPs and acquirers based on cost, success-rate, BIN, currency, region or merchant-defined rules, the core orchestration use case..
Medium-low globally, but high within tier-one airline payments.
As a payment orchestration platform sitting between airline merchants and the global PSP/acquirer network, Cellpoint touches the full set of PCI- and PII-sensitive data classes: Payment instruments: Card PANs / expiry / CVC (tokenized into Cellpoint vault tokens and / or network tokens), bank account / IBAN data for SEPA / direct-debit / Pix / PSE flows, wallet tokens (Apple Pay, Google Pay), local APM identifiers (UPI VPA, GrabPay account refs)..
Founded 2007. Cellpoint is mid-generation: meaningfully more modern than the legacy airline-payments stacks it competes with (ACI, Worldline, Outpayce), but architecturally older than Stripe / Adyen / Primer.
API is XML-based at a time when virtually every modern payments API (Stripe, Adyen, Checkout.com, Braintree, Primer) is REST/JSON, increases integration effort for engineers who haven't written XML payment code in a decade. Custom HMAC scheme (`x-cpm-sec-token` = SHA-256 of whitespace-stripped body + Cellpoint-issued salt) is non-standard; bugs in body normalization (e.g., whitespace, encoding) silently produce 401s that are hard to debug. Full sourced list under Sources below.
Common alternatives include IXOPAY, Spreedly, Primer, Gr4vy, Rapyd, PPRO. Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.
Yes. Supergood maintains an unofficial Cellpoint Digital API and MCP server so AI agents and internal tools can read and write Cellpoint Digital data. See the Cellpoint Digital integration docs at supergood.ai/docs/cellpoint-digital-api.