// payments · collections · peru
Payment gateway implementation in Peru
So your system collects on its own — and knows that it did, without anyone checking a receipt.
Adding a payment button is easy. The hard part is making the charge part of a flow: an enrollment that advances by itself when the payment lands, a procedure that unlocks without anyone eyeballing a receipt, and a month that closes without manual reconciliation.
We are a Solution Partner of several gateways. That means we gain nothing by pushing you toward one: we tell you which fits with the full math on the table, and we have a direct line to each one's technical team. We have taken Culqi and Niubiz to production, and connected the result to SAP Business One so every charge invoices itself.
// what we do
What the service includes.
The gateway that suits you, not the one that suits us
Being a partner of several means the choice gets made on your average ticket, your volume and your settlement delay — not on the fee table.
Public-sector collection
A public entity cannot contract a commercial gateway: it collects through Banco de la Nación. We integrate that collection into your system so the receipt stops being a piece of paper and becomes a queryable record.
Tokenization without touching card data
The card never reaches your servers: embedded checkout and tokenization, which is what keeps your PCI DSS questionnaire short.
Webhooks that don't lose a payment
Idempotency, retries and state reconciliation — so a charge approved at the gateway is never lost inside your system.
Yape, Plin and cash
The wallets that move Peru and the cash networks, through whichever rail supports each one.
Charging from abroad
Stripe and Mercado Pago when you sell outside Peru, alongside the local rails.
The charge that invoices itself
Every payment tied to its receipt, its SUNAT electronic invoice and its bank reconciliation. Without that you have a payment button, not an integration.
- Culqi
- Niubiz
- Izipay
- Kushki
- ProntoPaga
- Yape
- Banco de la Nación
- SUNAT
- SAP Business One
// how we work
From the first meeting to production.
- 01
Pick the collection route
Before the gateway comes the question of who you are: a public entity collects through Banco de la Nación and a private company picks a gateway. They are two different integrations and confusing them costs the project.
- 02
Onboarding and credentials
The commercial process runs in parallel with development. With Niubiz it takes longer than with Culqi, and knowing that upfront avoids promising a date that is not ours to promise.
- 03
Charging with the card off your servers
The provider's checkout and tokenization. It is what keeps your PCI DSS scope manageable, and it is decided at the start or it costs triple.
- 04
Webhooks and idempotency
Acknowledge first, process later, with a record of what was already handled. The moment you accept an asynchronous method like Yape or a bank deposit, the browser stops being a source of truth.
- 05
Reconciliation and invoicing
The cross-check between what the gateway or the bank says and what your database says, plus the receipt that issues itself. That is the part almost nobody writes about, and the part that breaks.
When you do not need to implement a gateway
If you sell little and sporadically, a payment link generated by the gateway itself solves the problem without writing a line. Implementing makes sense when the charge is part of a flow —an enrollment, a procedure, a subscription— and you need the system to know it was paid in order to continue on its own. And if your average ticket is very low, run the math first: the fixed fee takes more than you think.
Senior engineering
Whoever designs your system writes it. No juniors learning at your expense.
The code is 100% yours
We hand over the repository and the documentation. No lock-in.
Honesty
We tell you where it’s not worth spending — even if that’s hiring us.
// real cases
Systems we’ve already built.
collections · public sectorAn entire university’s collections, in real time
View case
enrollment · sports clubA whole club’s enrollment, no crashes on peak day
View case
Want to go deeper? What it really costs to charge online in Peru.
// frequently asked questions
What people usually ask us.
Which gateways do you work with?
Culqi and Niubiz in production, and we are a Solution Partner of several more — Kushki and ProntoPaga among them. We also work with Izipay, Yape, Plin, Stripe and Mercado Pago. Being a partner of several is exactly what lets us tell you honestly which one fits your case.
Culqi or Niubiz?
It is a decision about stage. Culqi wins when you need to ship fast and your volume does not yet justify negotiating a rate; Niubiz wins when volume allows negotiation, when approval rates on Peruvian cards matter, or when anti-fraud carries weight.
We are a public entity — can we use a gateway?
Generally not directly: public entities handle their funds through Banco de la Nación, so the payment happens outside your systems and arrives as a document. What you can do —and what we solved at UNJFSC— is integrate that collection into your platform, so any department validates the payment in real time instead of trusting a piece of paper.
Do I have to comply with PCI DSS?
Any online payment operation is subject to PCI DSS, but the expensive part is avoidable: with embedded checkout and tokenization the card data never touches your server, which drastically reduces your scope.
How long does a payments implementation take?
3 to 6 weeks for the technical part. Commercial onboarding with the gateway runs in parallel and usually sets the real launch date, especially with Niubiz.
Can I charge with Yape or Plin from my system?
Yes, through the gateways that support them or directly against the bank's API when volume justifies it. Plin has a caveat: it is not an app but a shared feature inside each bank's own app, so you charge those users through the interoperable QR, not by integrating something per bank.
Can the charge invoice itself?
That is the goal. We connect the payment to SUNAT electronic invoicing and, if you use it, to SAP Business One, so nobody keys a receipt again.
Let’s talk about your project.
You talk with the engineer who’d design your system, not a salesperson. No strings attached.