LunaPay® · Documentation

From your first payment to your own integration.

Download OpenAPI 3.1

Reviewed on 2026-09-19

Checkout and confirmations

The server calculates the order from the merchant’s own prices.

Run examples on your server with your own sandbox data. Never include keys in the frontend. This documentation does not enable live operations.

Create a checkout

With an approved customer, price and contract, create a session on your server. Replace example identifiers with your sandbox UUIDs. The response contains data.url to share with the buyer.

Server example
curl "https://payments.lunapay.ar/v1/checkout-sessions" \
  -H "Authorization: Bearer $LUNAPAY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: sandbox-order-00001" \
  -d '{
  "reference": "sandbox-order-00001",
  "contractId": "CONTRACT_UUID",
  "customerId": "CUSTOMER_UUID",
  "currency": "ARS",
  "items": [
    {
      "priceId": "PRICE_UUID",
      "quantity": 1
    }
  ]
}'

Check the status

Retrieve the payment by ID. A successful browser return, screenshot or session creation does not credit money. For uncertain outcomes, query and reconcile before trying another charge.

Server example
curl "https://payments.lunapay.ar/v1/payments/PAYMENT_UUID" \
  -H "Authorization: Bearer $LUNAPAY_API_KEY"

Refunds

Requesting a refund does not confirm execution. It requires a financial scope delegated by owner/admin with MFA, provider capability and contractual policy evidence. Partial refunds and refunds after payout remain auditable.

Server example
curl "https://payments.lunapay.ar/v1/refunds" \
  -H "Authorization: Bearer $LUNAPAY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: sandbox-refund-00001" \
  -d '{
  "orderId": "ORDER_UUID",
  "amountMinor": "10000",
  "reason": "Buyer request",
  "feePolicy": "proportional",
  "policyEvidence": "ACCEPTED_CONTRACT_VERSION"
}'

Development contract · source: Payments · 9f82d06

Next guideSubscriptions and installments