Skip to main content
The Payin module generates QR codes to receive payments in Bolivia. Authenticate with POST /v3/auth/login and send Authorization: Bearer {accessToken} with each request.

Create a QR Deposit

Conditional fields by fundingSource

fundingSource, referenceId (1–100 characters), and fiatCurrency: "BOB" are always required. country defaults to BO. description accepts up to 60 characters. qrExpirationTime uses HH:MM:SS and defaults to 00:15:00. Optional fields may be omitted; null is not accepted. With conversion, depositAddress must be non-empty and the fiat amount is calculated from the crypto amount, exchange rate, and fees.

Request (fundingSource: conversion)

Request (fundingSource: balance)

Response

Display qrCodeBase64 to the customer. Creating the QR returns HTTP 201; payment confirmation arrives through a transaction_updated webhook. See Webhooks for the notification contract and QR API reference for the complete schema.

ACH Deposits

ACH deposits are currently restricted to the dashboard. This endpoint is not available for direct partner integrations.
This flow generates a crypto address and amount to fund the business merchant account in BOB. amount is the BOB amount to receive. externalReference must be unique (1–100 characters), and blockchain must be Ethereum or Polygon.

Response: HTTP 201

After the full crypto amount is confirmed, the ACH transfer is requested. Amounts in the response are decimal strings, and status changes are notified through transaction_updated. An existing external reference returns HTTP 409.

Errors

QR requests return HTTP 400 for validation errors, 401 for authentication failures, 404 when the provider cannot find the transaction, 422 for a permanent rejection, 500 for an internal error, and 503 when the provider is unavailable. Review the API reference for response bodies.