cellulant

Integrate Cellulant Tingg checkout for cross-border African payments via API.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/AfricanDigitalAssetFramework/africa-stack-skills --skill cellulant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cellulant
Source: https://github.com/AfricanDigitalAssetFramework/africa-stack-skills/tree/main/east-africa/cellulant
Command: npx skills add https://github.com/AfricanDigitalAssetFramework/africa-stack-skills --skill cellulant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable developers to integrate Cellulant Tingg checkout for cross-border Africa payments with a single API, eliminating bespoke integrations across many payment providers.

Core Features & Use Cases

  • Unified cross-border checkout across 25+ African countries via Tingg v3.
  • OAuth 2.0 bearer token authentication, token management, and secure API calls.
  • Webhook-driven reconciliation with idempotent processing and reliable status updates.

Quick Start

Obtain an OAuth token and initiate a Tingg v3 checkout request to start a cross-border African payment.

Frequently Asked Questions about cellulant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate cross-border Africa payments into my application?

Cross-border Africa payments integrate via a single API that initiates Cellulant Tingg checkout across 25+ countries. It uses OAuth 2.0 bearer token authentication, eliminating the need for bespoke integrations across multiple regional payment providers.

How do I handle webhook acknowledgments for African payment gateways?

Handle webhook acknowledgments with diligent, idempotent processing to ensure reliable status updates. This prevents duplicate transactions during reconciliation when receiving automated payment notifications from the checkout API.

What base URLs are needed for sandbox testing and production checkout?

Sandbox testing uses the base URL https://api-approval.tingg.africa/v3, while production checkout requires https://api.tingg.africa/v3. You must obtain OAuth client credentials to authenticate API calls in both environments.

Does this unified checkout support querying transaction statuses and listing available payment methods?

This unified checkout supports status queries, transaction listing, and retrieving available payment methods. You can programmatically track payment lifecycle updates and display localized payment options to users across supported African regions.