Snippe
Mobile collections. Mobile and bank disbursements. Balance, list, status, and payout fee-quote routes.
- No hosted checkout or session flow is enabled
- Card and dynamic-QR creates are not supported
- Connected-account eligibility still applies
Payment connections, without pretending to be the payment provider.
CamelPay is a connector API. It gives an app a scoped, consent-led way to work with a user’s own Snippe or Abliner account.
One connector layer for a user-authorized account.
An application requests a user’s permission, obtains scoped access, and sends a supported request to CamelPay. CamelPay validates and routes it to that user’s connected provider.
The provider runs the payment. Its account rules, fees, availability, delivery, reversals, settlement, and final status remain with the provider.
PROVIDER COVERAGE
Know exactly what each adapter supports.
The integrations are intentionally specific; supported methods are different across providers.
Abliner
Mobile, card, and dynamic-QR deposits. Hosted checkout. Mobile and bank withdrawals.
- Also supports status, fee preview, and mobile lookup routes
- History uses a bounded recent feed
- Account eligibility and provider terms still apply
CLEAR ROLES, SAFER FLOW
Give every part of the flow a job.
Your app owns the customer experience. CamelPay handles the connector layer. The user chooses which provider account to connect. The provider owns payment execution and its outcomes.
Connection secrets are kept server-side and are not returned by read endpoints. Production storage encryption must be configured by the API operator.
A GOOD PLACE TO BEGIN
How it worksUnderstand the flow before you ship.
See the consent, routing, and callback steps in one place.