SBS Resolution 2660-2015: Peru AML and customer due diligence guide (2026)

In forceLast reviewed:

What the SBS regulation requires for identifying and verifying customers in Peru, what changed on October 29, 2026 in the simplified insurance regime, and how to check DNI, RUC and lists by API.

Status as of November 17, 2026: the LA/FT risk-management regulation approved by SBS Resolution No. 2660-2015 is in force. The latest related change is SBS Resolution No. 02580-2026, published in El Peruano on October 29, 2026 and in force the next day: it expands the insurance products that may use the simplified regime in article 31 and repeals Circular S-661-2016.

If your firm is supervised by the SBS, Resolution 2660-2015 requires you to identify the customer, verify their identity, rate their risk, screen the Annex 1 lists and keep evidence for at least 10 years. This guide summarises the due-diligence duties, what changed in October 2026 and how to run DNI, RUC, biometrics and list checks by API.

What SBS Resolution 2660-2015 is

It approves the Regulation on Money-Laundering and Terrorist-Financing Risk Management. The consolidated text we use is version 5.0 published by the SBS (the last direct amendment of the Regulation we found is SBS Resolution 1743-2020). The issuer is the Superintendencia de Banca, Seguros y AFP.

Who must comply

Article 1 covers the firms in articles 16 and 17 of Peru’s General Financial System Law (banks, financieras, municipal and rural savings banks, EDPYMEs, insurers and others), plus Banco de la Nación, Banco Agropecuario, FOGAPI, the AFPs, COFIDE, Fondo Mivivienda and insurance brokers. Brokers have their own simplified system in articles 64 to 67.

Other sectors — casinos and online gaming under SBS Resolution 01015-2026, cooperatives and other obligated parties — have their own rules, with similar KYC, PEP and list logic. 2660 does not apply to them directly; we mention them only as context.

The three stages and the three regimes

Article 29 splits customer due diligence (CDD) into identification, verification at onboarding and ongoing monitoring. If CDD cannot be completed, the relationship must not start or must be ended, and a suspicious-transaction report should be considered.

RegimeWhat it requiresArticles
GeneralFull data for individuals (name, ID type and number, nationality and residence, address, phone or email, purpose, occupation, PEP status and representatives) and for companies (legal name, RUC, business purpose, shareholders above 25% flagging any PEPs, representatives and powers, address). Every check is recorded (place, date, time and result) in the customer file, on paper or electronically. Every customer gets an LA/FT risk rating.30.1, 30.2, 30.3, 30.5; risk in art. 22 and Annex 3
SimplifiedA reduced data set (name, ID type and number, address). Showing the identity document is still required. It needs SBS authorisation per product. This is the regime that SBS Resolution 02580-2026 expands for certain insurance products.31
EnhancedMandatory, among others, for non-residents, non-domiciled companies, trusts, non-profits, PEPs and their relatives or spouse, companies with 25% or more PEP ownership, customers linked to FATF non-cooperative or OFAC-sanctioned countries, and customers under an LA/FT investigation.32

Article 30.6 requires you to keep data current, at a frequency set by risk. Article 28 imposes a standing duty to identify the beneficial owner (the natural person with ultimate control) and to take reasonable steps to verify their identity.

What changed on October 29, 2026

SBS Resolution 02580-2026, in force since October 30, 2026, expands the list of insurance products that may use the simplified regime in article 31 and repeals Circular S-661-2016. That does not remove the ID check: article 31.4 still requires the identity document to be shown. For insurers and bancassurance channels, the practical change is to remap which products need full CDD and which can follow the simplified path, without stopping the DNI or residence-card check.

Lists, staff and suppliers

Article 11(g) and Annex 1 require screening, among others, the OFAC SDN list, UN Security Council lists (Resolution 1267 and others) and proliferation-financing lists. That check applies at onboarding, in staff due diligence (article 35: a copy of the ID, police and criminal records, and Annex 1 list checks at hiring and afterwards) and in supplier due diligence (article 36: name, RUC, ID, address and list checks). Article 23 requires an LA/FT risk assessment before launching new products or technologies.

Infractions and penalties

The penalties are not in 2660 itself. They sit in the SBS Infractions and Sanctions Regulation, SBS Resolution 2755-2018 (consolidated text v34.0 of 2026). Infractions are minor, serious or very serious (article 4). Article 18 of that regulation says a separate SBS resolution will set the fine ranges; until one is issued, the Third Final Complementary Provision keeps article 10 of SBS Resolution 816-2005 in force for those ranges.

SeverityCompany (legal person)Directors, managers and staff
MinorA warning and/or 10–50 UITA warning and/or 0.5–3 UIT
Serious20–100 UIT3–50 UIT, with possible registry suspension of up to 6 months
Very serious30–200 UIT5–100 UIT, with possible suspension or cancellation of the authorisation, removal and disqualification

The 2026 UIT is S/ 5,500, under Supreme Decree No. 301-2025-EF, published on December 17, 2025. On that UIT, 20–100 UIT is S/ 110,000–550,000 for a company on a serious infraction, and 30–200 UIT is S/ 165,000–1,100,000 on a very serious one. Those sol figures are illustrative: article 20 of 2755-2018 uses the UIT in force on the date the resolution ending the administrative instance is notified. COOPACs have their own scale in article 19. Among the serious common infractions in Annex 1 is failing customer due diligence, including identifying enhanced-regime customers (PEPs) and the beneficial owner. Failing to file a ROS with the UIF is a very serious infraction.

How Verifik fits these controls

Verifik does not replace the compliance officer, does not file ROS reports with the UIF and does not currently offer a Peru PEP list. The SBS itself has said there is no official list of PEP names, only a list of positions (SBS Resolution 4349-2016, amended by SBS Resolution 02868-2025, with a 2-year look-back). Verifik’s only PEP endpoint is Colombia’s; the country=PE filter on GET /v2/cia-world-leaders covers only heads of state, ministers and central-bank authorities, a much smaller set than that rule. What you can automate is identity and RUC verification, biometrics and OFAC/UN screening, and keep signed evidence of each query.

DutyControlWhat Verifik offers
Identify and verify individuals (arts. 30.1 and 31.4)Check the DNI against RENIECGET /v3/pe/cedula and, for extended detail, /v3/pe/cedula/extra
Foreign residents (arts. 30.1 and 32.a)Check the residence cardGET /v2/pe/foreigner-id/ce
Companies, KYB and suppliers (arts. 30.2, 31.3 and 36)Check the RUC at SUNATGET /v3/pe/company
Remote verification (arts. 29.1 and 30.5)Confirm the person is the document holder and is presentsmartENROLL and POST /v2/face-recognition/compare-with-liveness
Annex 1 lists (arts. 11.g, 32, 35 and 36)Screening at onboarding and afterwardsGET /v2/ofac and GET /v2/onu
Evidence and audit trail (arts. 30.5 and 54–55)A dated, signed result, retrievable for at least 10 yearsEvery response carries a “Certified by Verifik.co” signature

For batch or no-code checks, smartCHECK. To re-authenticate a customer who has already been verified, HumanAuthn.

1. Chain DNI, liveness and list checks

The DNI documentation requires documentType=DNI and an 8-digit documentNumber. The example uses a test identifier from the docs and then queries OFAC and the UN lists:

import axios from "axios";

const headers = {
  Accept: "application/json",
  Authorization: `Bearer ${process.env.VERIFIK_TOKEN}`,
};

const { data: dni } = await axios.get("https://api.verifik.co/v3/pe/cedula", {
  params: { documentType: "DNI", documentNumber: "44868598" },
  headers,
});

const { data: face } = await axios.post(
  "https://api.verifik.co/v2/face-recognition/compare-with-liveness",
  {
    probe: "<base64>",
    gallery: ["<base64>"],
    search_mode: "FAST",
    liveness_min_score: 0.6,
    compare_min_score: 0.8,
  },
  { headers: { ...headers, "Content-Type": "application/json" } }
);

const params = { documentType: "DNI", documentNumber: "44868598" };
const { data: ofac } = await axios.get("https://api.verifik.co/v2/ofac", { params, headers });
const { data: onu } = await axios.get("https://api.verifik.co/v2/onu", { params, headers });

console.log({ dni, face, ofac, onu });

2. Look up a company’s or supplier’s RUC

curl -G "https://api.verifik.co/v3/pe/company" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $VERIFIK_TOKEN" \
  --data-urlencode "documentType=RUC" \
  --data-urlencode "documentNumber=20605980008"

Implementation checklist

  • Confirm that your firm falls under article 1 of 2660 and, if you are an insurance broker, review the simplified system in articles 64 to 67.
  • Set the regime for each product or customer: general, simplified (with SBS authorisation) or enhanced.
  • Capture the minimum data in article 30.1 (individuals) or 30.2 (companies), including the PEP declaration and shareholders above 25%.
  • Check the DNI against RENIEC or the residence card, and the RUC against SUNAT.
  • If onboarding is remote, add face comparison with liveness and store the query identifier.
  • Screen OFAC and the UN lists at onboarding, for staff and for suppliers, and set a refresh frequency by risk.
  • Identify the beneficial owner and take reasonable steps to verify their identity (article 28).
  • Assign an LA/FT risk rating to every customer (article 30.3) and keep data current at the matching frequency (article 30.6).
  • Keep evidence of each check (place, date, time and result) in a retrievable form for at least 10 years, with quarterly backups available within 48 business hours (articles 54 and 55).
  • Document escalation to a ROS with the UIF when CDD cannot be completed or an alert appears.
  • If you are an insurer, remap the products that now fall under the simplified regime because of SBS Resolution 02580-2026, without dropping the identity-document check.
  • Do not treat PEP detection as solved by an API alone: there is no Peru PEP-list endpoint today.

Frequently asked questions

Who supervises this rule?

The Superintendencia de Banca, Seguros y AFP (SBS). Suspicious-transaction reports are filed with UIF-Perú.

Can onboarding be done fully remotely?

The regulation requires identification, verification and evidence (articles 29 and 30.5), and article 31.4 still requires the identity document to be shown even under the simplified regime. It does not forbid a remote flow if those checks are met. A common design is to validate the DNI or residence card, compare a selfie with liveness and store the signed result.

What is the simplified regime, and what changed in October 2026?

Article 31 allows a reduced data set, with SBS authorisation per product, but still requires the identity document to be shown. SBS Resolution 02580-2026, in force since October 30, 2026, expands the insurance products that may use that regime and repeals Circular S-661-2016.

What does a PEP trigger?

Article 32 makes enhanced due diligence mandatory for PEPs and their relatives or spouse, and for companies with 25% or more PEP ownership, among other cases. You must apply enhanced measures, not only collect a declaration. Verifik does not currently have a Peru PEP-list endpoint; the SBS has said there is no official list of PEP names, only a list of positions.

Which lists does the SBS require?

Annex 1 and article 11(g) include the OFAC SDN list, UN Security Council lists (Resolution 1267 and others) and proliferation-financing lists, among others. The check applies to customers, staff and suppliers.

Do casinos and online betting have to follow 2660?

Not directly. Those sectors have their own rule, SBS Resolution 01015-2026, with similar KYC, PEP and list logic. 2660 applies to the firms in article 1 (the financial system, insurance, AFPs and the entities listed there).

Does a KYC API replace the compliance officer?

No. The API automates identity, RUC, biometrics and list checks and leaves evidence. The compliance officer, the manual, risk rating, ROS filings and 10-year retention remain the supervised firm's responsibility.

Other regulations

See all regulations and filter by country or topic →

Need identity verification and consent that hold up to an audit?

Book a meetingExplore smartCHECKAPI docs

Talk to a compliance specialist

Tell us about your onboarding flow and we will map the identity checks, biometrics and consent records you need.

Sources

  1. SBS Resolution No. 2660-2015 — consolidated text v5.0 (Spanish)
  2. SBS Resolution No. 02580-2026 (El Peruano, 29 Oct 2026, Spanish)
  3. SBS Resolution No. 01015-2026 (casinos and online gaming, Spanish)
  4. SBS Resolution 2755-2018 — Infractions and Sanctions Regulation (v34.0, 2026, Spanish)
  5. Supreme Decree No. 301-2025-EF — 2026 UIT (El Peruano, 17 Dec 2025, Spanish)
  6. SUNAT — UIT value (Spanish)
  7. Verifik docs — Peru DNI
  8. Verifik docs — SUNAT RUC
  9. Verifik docs — OFAC lists

Disclaimer: This content is for information only and is not legal advice. It summarizes the official text as of the last-reviewed date; always check the official source and your legal counsel before making compliance decisions.