Skip to content

Payment methods · Paraguay

SIPAP in Paraguay: real-time and high-value payouts

Pay Paraguayan bank accounts through SIPAP, in real time up to PYG 5,000,000, and use the high-value flow for larger amounts, all with the same code.

Contact salesGo to our docs
  • Payout rail
  • Paraguay
  • Payout

Key facts

SIPAP and SPI at national scale

Figures published by the Central Bank of Paraguay.

What it is

The payout rail for bank accounts in Paraguay

SIPAP is the interbank payment rail used for bank transfers in Paraguay. With Localpayment you send payouts to beneficiary bank accounts with a single code (0160). As documented, payouts are real-time up to PYG 5,000,000, and a high-value flow applies to amounts above that. Paraguay is covered for payouts only.

  • Real-time SIPAP payouts up to PYG 5,000,000
  • A high-value flow for amounts above PYG 5,000,000, under the same code
  • Final status by signed webhook; RUC and CI document types

How it works

How a SIPAP payout works

Actors and steps follow the documented flow. The final status always arrives by signed webhook.

  1. 1

    Your businessLocalpayment:

    Sends the payout request

    POST /api/payout/ with the beneficiary details, amount and externalId. Compliance checks run; with requireAuth, a second approver signs off before funds move.

  2. 2

    LocalpaymentBank · SIPAP:

    Locks the funds and sends the instruction

    The payout moves from Locked to In Progress over SIPAP.

  3. 3

    Bank · SIPAPBeneficiary:

    Credits the beneficiary

    Timing depends on the rail; see the key facts below.

  4. 4

    LocalpaymentYour business:

    Webhook: payout completed

    Localpayment updates the payout to its final status. Signed webhook with the final status; the proof of payment can be downloaded.

Simplified diagram. Timing depends on the rail and the bank; see the key facts below.

How it works

See SIPAP in action

A simplified, fictitious walkthrough. Names and amounts are examples.

  1. 1Comercio EjemploYour platform sends a PYG 1,500,000 payout through SIPAP.
  2. 2Banco EjemploThe beneficiary sees the PYG 1,500,000 credit in their account or wallet.
  3. 3Payout completedYour system receives the signed webhook and updates the order.
Contact sales

Key facts

SIPAP: key facts

  • Country

    Detail
    🇵🇾 Paraguay

  • Currency

    Detail
    PYG

  • Direction

    Detail
    Payout only

  • Bank transfer (SIPAP)

    Detail
    Real-time, 24/7 · Up to PYG 5,000,000

  • SIPAP high-value

    Detail
    Real-time, 24/7 · Above PYG 5,000,000

Taken from the Localpayment documentation for each country. Limits and availability can change; confirm them with your account manager.

Consumer experience

What your customer sees with SIPAP

Authorization, limits and refunds as documented on docs.localpayment.com. Limits are shown only where the documentation states them.

  • How the customer authorizes

    Nothing is required from the beneficiary. You create the payout with POST /api/payout/ (code 0160) with the account number, bank and RUC or CI of the beneficiary; if double-signature approval is enabled, a second user approves it in the Business Portal. The beneficiary simply receives the credit in their bank account.

  • Documented limits

    Bank transfer (SIPAP) (Payout): Up to PYG 5,000,000 · SIPAP high-value (Payout): Above PYG 5,000,000. Per transaction, as published in the documentation; contractual limits may differ.

  • Refunds and returns

    If the beneficiary bank rejects a completed payout days later (closed or invalid account), the funds come back to your Localpayment balance and the payout moves to Returned, notified by webhook. A recall for wrong beneficiary data is a manual request to our operations team and is not guaranteed.

Integration checklist

Go live with SIPAP in five steps

The same sequence for every rail. Watch the animated checkout for this country before you build.

  1. Get Stage credentials

    Request access, receive sandbox credentials and obtain a JWT with POST /api/token/.

  2. Fund your balance

    Payouts are debited from your Localpayment balance in the local currency; fund it locally or via Wire In with FX.

  3. Send the payout

    POST /api/payout/ with the beneficiary, document, account or alias, amount and a unique externalId.

  4. Approve and track

    With requireAuth a second user approves; follow Received, Locked, In Progress and Completed by signed webhook.

  5. Watch the animated flow

    Every method of this country, screen by screen, in the checkout experiences gallery.

History

How Paraguay moved its payments onto SIPAP

Sources: Banco Central del Paraguay, institutional releases on SIPAP, SPI and the SIP identity.

  1. SIPAP starts operating

    The Central Bank of Paraguay launches the Paraguayan Payment System (SIPAP) on 23 November 2013, with real-time gross settlement between participating institutions.

  2. Instant Payment System (SPI)

    The central bank launches the SPI within SIPAP: low-value transfers between accounts at different institutions, credited in seconds, around the clock.

  3. More than 170 million instant payments

    The SPI processes over 170 million transactions, 37% of all low-value operations by count, with an average transaction time of 2.8 seconds.

  4. SIPAP becomes SIP

    The central bank presents SIP as the new identity of the Paraguayan Payment System, with an interoperable QR hub scheduled to roll out from May 2026.

Why Localpayment

Why use SIPAP with Localpayment

  • One API for pay-ins and payouts

    SIPAP runs on the same API as every other method: POST /api/payin/ to collect, POST /api/payout/ to pay out, and new markets by configuration.

  • Webhook status on every transaction

    Every status change is pushed to your endpoint, signed with HMAC-SHA256, so you can verify and automate.

  • Reconciliation in the Business Portal

    Match every transaction through your externalId and our internalId, with Business Portal reports and balance APIs.

Keep exploring

FAQ

SIPAP: frequently asked questions

How fast are SIPAP payouts?

SIPAP payouts (code 0160) are real-time up to PYG 5,000,000. The final status always arrives by signed webhook.

What about amounts above PYG 5,000,000?

A high-value flow applies above PYG 5,000,000, under the same code 0160. It is also real-time; confirm timing for your contract with your account manager.

Can I collect payments in Paraguay?

Paraguay is covered for payouts only. Send them with POST /api/payout/ and receive the final status by signed webhook.

Which beneficiary data does a SIPAP payout need?

The beneficiary’s full name, document type and number (RUC or CI), bank and account number. Validate the document format before sending to avoid rejections.

What are the payout statuses?

100 Received, 101 Locked (passed compliance), 102 In Progress (sent to the bank), 200 Completed (credited) and 300 Rejected, each delivered by signed webhook.

Can I pay out in USD in Paraguay?

The documented SIPAP payout is in guaraníes (PYG). Confirm any other currency with your account manager before building for it.

What happens if the beneficiary account is wrong?

The payout is rejected by the receiving bank and you get status 300 by webhook with the reason. The funds remain in your balance; correct the data and create a new payout.

Send payouts via SIPAP

Tell us your markets and volumes. We start you on Stage (sandbox) credentials and guide you to go-live.

Contact salesGo to our docs

How can we help?

Download your copy

Leave your details and get the full edition instantly.