Skip to main content

Payment Provider Integration

As a payment provider, you integrate your network of physical points (stores, kiosks, agents) with Pago46 to process cash collections and disbursements generated by merchants.

Available services​

Pay-In (Collections)​

Process cash payments from end users at your physical points.

Flow: The user presents a code → you validate and lock the order → you receive the cash → you confirm the transaction.

View Pay-In documentation

Pay-Out (Disbursements)​

Disburse cash to end users at your physical points.

Flow: The user presents a code → you validate and lock the order → you deliver the cash → you confirm the transaction.

View Pay-Out documentation

Integration flow​

The architecture is server-to-server with HMAC SHA-256 authentication.

Integration steps​

  1. Get your credentials - Receive your Provider-Key and Provider-Secret
  2. Register your networks - Send us your list of networks/subnetworks to get network_id
  3. Implement HMAC authentication - View guide
  4. Query orders - Use GET /providers/orders/{type}/{code}/
  5. Process transactions - Use start-payment and confirm-payment
Locking mechanism

Locking applies to both Pay-In and Pay-Out. When you call start-payment, the order is reserved for your network until you confirm or cancel.

Networks and subnetworks

To call the endpoints, you need a valid network_id. Send us your list of networks/subnetworks so we can register them and assign the IDs.

Environments​

EnvironmentURLUsage
Sandboxapi.dev.pago46.ioDevelopment and testing
Productionapi.prd.pago46.ioReal operations

→ View environment details

Operational monitoring

For day-to-day operations in cashier/support teams, review the Service Status page and subscribe to email or Slack alerts to stay informed about incidents and maintenance.

Order lifecycle​

The state diagram is the same for Pay-In and Pay-Out. Each arrow shows the action that triggers the transition: the ones labeled with an endpoint name (start-payment, confirm-payment, cancel-payment) are the ones you, as a provider, call via API; the rest happen automatically or are triggered by the merchant.

From which state can I act?

The action you can take depends on the order's current state:

  • Take an order → start-payment, available only from READY.
  • Release / "return" an order → cancel-payment, available only from PAYMENT_STARTED, before confirming, and only to the provider that locked the order. The order goes back to READY and is available again. If another provider locked it, you cannot act on it.
  • Confirm the transaction → confirm-payment, available only from PAYMENT_STARTED. The order moves to COMPLETED. Confirm only once the cash has changed hands: for Pay-In when you received it, for Pay-Out when you handed it out.
  • COMPLETED, CANCELLED, and EXPIRED are final states: they allow no further transitions.
No API reversals

This is a cash operation and confirmation is immediate: an order in COMPLETED cannot be returned or reversed through the API. Any later adjustment is resolved in the settlement process agreed upon with the Pago46 team. That's why confirm-payment must always reflect a real movement of cash.

Who can cancel an order?

As a provider you never move an order to CANCELLED: cancel-payment only releases it back to READY. A definitive cancellation is triggered by:

  • In Pay-In: the end user or the Pago46 team.
  • In Pay-Out: only the Pago46 team.

Merchants cannot cancel orders.

Coverage​

Pago46 operates in multiple countries across Latin America. View complete list.