The money goes straight to your account. We provide the API.

Camel Payment orchestrates your own Mercado Pago and Stripe accounts behind a single API for payments, refunds, and checkouts. We normalize statuses, errors, and webhooks; we never hold funds or keep balances.

The money

Your customer Pays ARS 15,000.00
direct, no middleman
Your Mercado Pago account The balance is yours

The data

Your backend POST /v1/payments
one API
Camel Payment status: approved
signed webhook
Your webhook payment.approved
Where the money goes and where the data goes.Camel Payment is not in the path of the money: it never holds funds or keeps balances.

Every provider speaks its own language.

Integrating two providers means maintaining two integrations. The same payment is written, approved, declined, and signed differently in each.

  • Amount

    Mercado Pago
    transaction_amount: 15000.00
    Stripe
    amount: 1500000
    Camel Payment
    amount: 1500000
  • Approved payment

    Mercado Pago
    status: approved
    Stripe
    status: succeeded
    Camel Payment
    status: approved
  • Insufficient funds

    Mercado Pago
    cc_rejected_insufficient_amount
    Stripe
    decline_code: insufficient_funds
    Camel Payment
    failure.code: insufficient_funds
  • Webhook signature

    Mercado Pago
    x-signature: ts=…,v1=…
    Stripe
    Stripe-Signature: t=…,v1=…
    Camel Payment
    X-Webhook-Signature: t=…,v1=…
  • Idempotency

    Mercado Pago
    X-Idempotency-Key
    Stripe
    Idempotency-Key
    Camel Payment
    Idempotency-Key

One API, several providers, your account.

Connect the accounts you already have. Camel Payment translates each call for the provider and always answers in the same shape.

  1. Connect your account

    Add your Mercado Pago or Stripe credentials. They are encrypted and only ever shown masked.

  2. Call one API

    POST /v1/payments with a pay_test_ or pay_live_ key. Same body for every provider.

  3. Get one result

    The same statuses in the response and the webhook, with the provider’s own alongside.

Switch providers: the response keeps its shape.

RequestPOST /v1/payments

curl https://api.camelpayment.com/v1/payments \  -H "Authorization: Bearer pay_test_…" \  -H "Idempotency-Key: order-1524" \  -d '{    "provider": "mercadopago",    "connection_id": "con_01JBX7P8H2D4",    "amount": 1500000,    "currency": "ARS",    "payment_method": {      "type": "card",      "token": "mp_card_token"    }  }'

Normalized responseSample data

{  "id": "pay_01JBX7Q2M4N8K5R6",  "object": "payment",  "provider": "mercadopago",  "amount": 1500000,  "currency": "ARS",  "status": "approved",  "provider_status": "approved",  "provider_payment_id": "1342345678",  "failure": null,  "created_at": "2026-11-12T15:04:05Z"}

We never touch your money.

Camel Payment is not a processor or a wallet. Your customers pay into your provider account; funds, balances, and payouts stay between you and the provider.

  • Encrypted credentials

    Provider keys are encrypted at rest with Fernet (AES-128 and HMAC-SHA256) in a versioned vault, shown masked, and rotatable.

  • Isolated environments

    Sandbox and production never share keys, connections, payments, or webhooks. A pay_test_ key cannot reach production.

  • Signed webhooks

    Every delivery carries X-Webhook-Signature, an HMAC-SHA256 of timestamp.body with an endpoint secret you see once.

  • Idempotent by default

    Same key and request return the original response; a different request gets a 409. Timeouts are reconciled, never retried blindly.

Made for the people who integrate.

What you need to debug a payments integration, in the same dashboard.

Webhooks with retries and replay

Retries with backoff and every attempt recorded. A replay creates a new delivery; the event is never duplicated.

payment.approved → https://your-store.example/webhooks

Sample
  1. Attempt 1 HTTP 500
  2. Attempt 2 HTTP 503
  3. Attempt 3 HTTP 200

X-Webhook-Signature: t=1794495847,v1=9f3c…

Replay: a new delivery of the same event, attempt 1 HTTP 200

Request log

Every API call with its method, path, status, and duration, per project and environment.

  • POST /v1/payments 201
  • GET /v1/payments/pay_01JBX7… 200
  • POST /v1/payments/pay_01JBX7…/refunds 201
  • POST /v1/checkouts 409

Pay links

A page to get paid under your name and brand, without writing code.

camelpayment.com/your-name

Also: projects with members and roles, hosted checkouts, billing, and a dashboard with sandbox and production.

Providers

Mercado Pago and Stripe are the foundation. PayPal, Ualá Bis, and wallets join on the same API.

  • Mercado Pago

    Checkout Pro and tokenized card payments across Latin America.

  • Stripe

    Payment Intents and hosted Checkout Sessions.

  • PayPal

    Buyer approval with Orders v2, capture, and refunds.

  • Ualá Bis

    Card payments through a hosted checkout in Argentina.

  • Apple Pay

    On your payment page, through your Stripe connection.

  • Google Pay

    On your payment page, through your Stripe connection.

Free to start. Then US$5 or US$10 a month.

Your plan follows what your account processes in production each month, across all your projects. You never pick one, and sandbox is always free.

  1. Free

    Under US$150 a month

    US$0 a month

  2. Starter

    From US$150 a month

    US$5 a month

  3. Growth

    From US$500 a month

    US$10 a month

No percentage and no per-payment fee from Camel. Your providers keep charging their own fees, as always.

Production volume this month

US$50

Charged payments minus refunds, in USD

Your month would cost

US$0

a month · Free

Camel invoices after the month closes, and you pay it through Camel like any checkout.

Accept your first payment today.

Create your account and start in sandbox. Move to production when your integration is ready.