Connect a user-owned account
Users authorize an app and link their own Snippe or Abliner account. Provider credentials stay on the server side.
PAYMENT CONNECTIONS, MADE CLEAR
Your app.
Their account.
One clear link.
CamelPay gives apps a consistent way to connect with a user’s own Snippe or Abliner account—without becoming a wallet or payment processor.
✓ User-owned accounts✓ Scoped app access✓ Provider-led outcomes
The CamelPay connector
C
CamelPay APIScoped connection
S
SnippeUser’s account
A
AblinerUser’s account
Connect · Authorize · Route
Not a wallet. Not a settlement promise. CamelPay connects apps to providers; execution, fees, availability, and settlement remain with each provider.
Understand the connectorA SMALLER GAP BETWEEN APP AND ACCOUNT
Fewer moving parts between your app and payments.
Connect the user’s provider account once, then work with a clear API surface for the operations that account supports.
Make one clear API request
Use scoped OAuth access to request supported collections, checkouts, payouts, and transaction status.
Keep responsibilities clear
CamelPay routes and validates the request. The connected provider executes it and controls the final outcome.
BUILT AROUND USER CHOICE
Let people connect the account they already use.
Your app stays focused on its own experience. CamelPay handles the connection layer between a user-authorized app and the user’s provider account.
- ✓Access is scoped through OAuth 2.0 with PKCE.
- ✓Provider secrets are not returned by connection reads.
- ✓Collection and payout outcomes remain provider-controlled.
A CLEAR, CONSENT-LED FLOW
From permission to provider response.
The connection model keeps the user, your application, CamelPay, and the provider in their proper roles.
01
User approves access
The app requests only the permissions it needs; the user authorizes the connection.
02
Your app makes a request
CamelPay checks scope and request details, then routes supported operations to the chosen provider.
03
Provider returns its result
The provider reports acceptance or a later status. Acceptance alone does not mean settlement.
SUPPORTED PROVIDER PATHS
Two adapters. Clear coverage.
Available payment methods differ by provider and connected account. CamelPay reports the provider’s response; it does not promise every rail is enabled.
Snippe
Mobile collections and mobile or bank disbursements, with status and fee-quote endpoints.
- Hosted sessions are not enabled
- Availability depends on the connected account
Abliner
Mobile, card, and dynamic QR deposits; hosted checkout; and mobile or bank withdrawals.
- Includes supported status and fee-preview routes
- Availability depends on the connected account
Details are based on the current CamelPay API and provider compatibility notes. Provider account eligibility, fees, limits, execution, and settlement are not set by CamelPay.
STRAIGHTFORWARD PLATFORM ACCESS
A clear yearly price.
One annual price for CamelPay access and the ability to connect apps to supported payment accounts.
See what’s includedTZS 25,000per year
✓ CamelPay platform access✓ Connect apps to supported providers✓ API, CLI, and MCP tools
Provider transaction fees, account terms, and settlement are determined by Snippe or Abliner. This site does not process your subscription.
GOOD QUESTIONS FIRST
Before you connect.
Does CamelPay hold or move my money?
No. CamelPay is a connector that routes supported requests to the user’s connected provider. The provider handles payment execution and settlement.
Which providers can I connect?
The current API supports Snippe and Abliner. Supported methods differ by provider; review the product page and provider notes before building.
Does the annual price include provider transaction fees?
The annual TZS 25,000 price is for CamelPay platform access and app connections. Provider fees and account terms are separate and are set by the provider.
Does a successful API response mean funds have settled?
No. A provider acceptance response is not proof of completed delivery or settlement. Your app should reconcile status with the provider.
READY TO BUILD?
Explore the flowStart with the connection model.
Read how CamelPay separates app authorization from provider execution, then explore the API contract.