# Peru

What you need to send to Peru on each channel: what is asked for, who files it, how long it takes and what happens if your sender isn't approved.

**Language:** en
**Audience:** platform
**Translation key:** platform.channels.countries.peru
**Search keywords:** Peru registration, send sms to Peru, Peru requirements, Peru rcs, sender Peru, Peru, PE, +51
**Docs index (every page):** https://docs.instasent.com/llms.txt
**This zone's index:** https://docs.instasent.com/platform/en/llms.txt
**This page:** https://docs.instasent.com/platform/en/channels/countries/peru/ (HTML) · https://docs.instasent.com/platform/en/channels/countries/peru.md (Markdown)
**Other language (es):** https://docs.instasent.com/platform/es/channels/countries/peru.md

{/* ─────────────────────────────────────────────────────────────────────────
    GENERATED FILE — DO NOT EDIT.

    Every edit here is overwritten by the next build, without warning.

    To change the facts block:  content/data/countries/<iso>.yaml
    To change the prose:        content/data/countries/prose/<iso>.en.mdx
    Then run:                   pnpm data:pages

    The authoring contract is docs/AUTHORING-COUNTRIES.md.
  ───────────────────────────────────────────────────────────────────────── */}

## What this country needs

### SMS

- **Your sender** — An alphanumeric sender is replaced by a number on delivery, so your brand doesn't travel as the sender. A [brand prefix](/platform/en/channels/sms/sms-essentials#how-your-sender-appears-abroad) keeps your name visible in the text.
- No registration needed — creating the sender is enough.

### RCS

- **What they ask for** — Proof of consent
- **Who acts** — You sign the paperwork and return it to us.
- **Have this ready** — An explanation of where and how you collect the phone number; The specific event that triggers each kind of message
- **Without an approved registration** — Nothing is sent to this country until the registration is approved.

Peru reviews consent in more detail than other markets. Saying where and how you collect the
number isn't enough: you have to state **which action or event produces each message**.

- **Authentication or OTP** — the screen where the user enters the phone number and the action
  that requests the code.
- **Transactional** — where the number came from and which service event generates the message,
  such as an order confirmation or a status change.
- **Promotional** — the express consent, and the campaign, automation or condition that starts
  the send.
- **Mixed use** — describe the consent and the trigger for each kind separately.

If what you provide isn't enough, we'll ask you to complete it before filing the registration.

---

This is one page of the Instasent documentation. For the complete machine-readable index of every guide and API reference, fetch https://docs.instasent.com/llms.txt — start there for full context.