Skip to main content

DEEPayment Merchant API

DEEPayment Merchant API provides unified endpoints for payments, payouts, subscriptions, order queries, balances, payout receipts, merchant webhooks, and Subscription Events. All requests use HTTPS + JSON. Protected business APIs are signed with the merchant Ed25519 key (RFC 9421), and POST bodies are encrypted with an X25519 sealed box; the platform SDK handles both.

Recommended path: generate keys, configure the SDK, create orders, handle webhooks, and use query APIs as the source of truth when callbacks are delayed or duplicated.

API Map​

Integration Path​

  1. Prepare merchant credentials

    Send production requests to https://panama.deepayment.com/api/v1. Get the Access Key and platform public keys during onboarding, upload your Ed25519 public key, and keep credentials separated by environment.

  2. Choose the business integration path

    Use Payments & Payouts for one-time orders, or the Subscription Quick Start for recurring billing and hosted Checkout.

  3. Sign the exact outgoing request

    Sign with your Ed25519 key over the RFC 9421 signature base and seal POST bodies to the platform X25519 key. The SDK does this for you.

  4. Create payment or payout orders

    Use merchantOrderNo as your idempotency key, and pass the lowerCamelCase method branch that matches the selected code.

  5. Handle webhooks and query recovery

    Verify signatures before posting final states. Use query APIs when callbacks are delayed, duplicated, out of order, or when create requests return 5xx.

Method Shape​

Order creation uses merchantOrderNo, currency, amount, webhookUrl, and a method object. Method objects follow code + lowerCamelCase branch:

{
"paymentMethod": {
"code": "PIX",
"pix": {
"payerCPF": "12345678901",
"payerName": "Joao Silva"
}
}
}

code uses uppercase enum values. Branch fields use lowerCamelCase, for example PIX -> pix, PSE -> pse, and BANK_TRANSFER -> bankTransfer.