> ## Documentation Index
> Fetch the complete documentation index at: https://docs.caratuva.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment links

> What your buyer sees on pay.caratuva.com, and how it gets them from invoice to paid.

A payment link is the URL Caratuva generates for every approved invoice. It points to a hosted payment page on `pay.caratuva.com` that walks your buyer from "I owe \$12,500" to "paid" — without installing anything, creating a Caratuva account, or holding a wallet.

You can deliver the link by:

* **The dashboard's "Invite buyer" button**, which sends an email magic-link from Caratuva.
* **Your own channel** — CRM, ERP, WhatsApp, in-app message. Copy the link from the invoice detail page.

Both paths land the buyer on the same hosted page.

## What the link looks like

```
https://pay.caratuva.com/r/<publicId>
```

The `publicId` is unguessable. The page is safe to share through any channel — it doesn't grant access on its own. To actually pay, the buyer must verify ownership of the email address on the invoice.

## What the buyer sees

### 1. The invoice summary

The landing page renders:

* Your trade name and logo (if one is on file for your organization).
* The invoice header, amount, and currency.
* The line items and any notes you wrote.
* A "Sign in to pay" call-to-action.

If the buyer arrives without a session, they see the summary in read-only mode and click through to sign in.

### 2. Email magic-link sign-in

The buyer enters the email address the invoice was addressed to. Caratuva emails them a one-time sign-in link that expires in 15 minutes and can be used once. Clicking the link signs them in and forwards them to the next step in their flow — identity verification, payment, or tracking, depending on where they are (it doesn't return them to the summary page). The session is a 30-day httpOnly cookie scoped to `pay.caratuva.com`.

If the email doesn't match the invoice's buyer email, the sign-in request is **rejected immediately** — no magic-link email is sent and the buyer sees an error on the sign-in form. This prevents anyone forwarded the link from gaining access.

### 3. KYC (first time only)

If this is the buyer's first Caratuva payment, they walk through identity verification. KYC is **mandatory on every payment surface** — there is no skip path, even for very small amounts or for invoices created via the API.

A returning buyer who has already verified — including from another seller's invoice — reuses their existing KYC and skips this step. They typically pay in seconds.

See [Buyer KYC](/buyer-kyc) for what we ask for.

### 4. Pay (FX quote + bank transfer)

On a single page, the buyer picks a sending currency and a bank rail (**ACH**, **wire**, or **SEPA** — card is not currently offered), then **locks an FX quote**: exactly how much they pay in their currency, the FX rate, and any fees. The locked quote has a 10-minute TTL — if the buyer waits too long, they lock a fresh quote (which may differ).

After confirming, the buyer is shown **bank-transfer instructions** (bank name, account number, routing/IBAN/SWIFT, and a reference code) and pays from their own bank. Once those funds arrive, we transfer them across borders and run the BRL payout to your registered PIX key.

### 5. Confirmation

When collection is complete, the buyer is redirected to your `returnUrl` (if you set one when creating the invoice). Otherwise they see a Caratuva confirmation page with the invoice receipt.

The seller-side timeline keeps moving from there — `fiat_received`, `offramp_pending`, `settled` — all asynchronously, with no buyer involvement. The buyer sees their part of the job as done as soon as their funds are collected.

## Branding

The buyer page shows your organization's trade name (in the header and the email magic-link template) and its logo, when one is on file. Configuring the logo or a brand color isn't yet self-service in the dashboard — contact support to set them up.

We deliberately keep the rest of the page consistent across sellers — that consistency is what makes returning buyers trust the page. They've been here before.

## Languages

The page auto-detects the buyer's browser language and serves Portuguese, English, or Spanish (more languages on the way). The buyer can switch from a footer dropdown.

## Mobile

The page works on any modern phone or tablet. KYC document capture uses the device camera directly — buyers do not need to email screenshots.

## What's NOT on the page

To keep the buyer focused on paying:

* No advertising, upsells, or cross-promotion.
* No links out to Caratuva marketing.
* No request for the buyer to "create an account" — they already have one, by virtue of clicking the link.

## Failure modes

What buyers see when something goes wrong:

| What happened               | What the buyer sees                                    |
| --------------------------- | ------------------------------------------------------ |
| Magic-link expired          | "This link expired. Request a new one."                |
| Email mismatch              | "This invoice was sent to a different address."        |
| KYC rejected                | "We couldn't verify your identity. Contact support."   |
| FX quote expired            | "This quote expired. Lock a fresh one to continue."    |
| Invoice cancelled by seller | "This invoice was cancelled. Contact the seller."      |
| Invoice expired             | "This invoice expired on \[date]. Contact the seller." |

All of these also fire a webhook to your ERP — see [Webhooks](/api-reference/webhooks).

## Customizing further

Most sellers don't need to customize beyond branding. If you want a fully embedded checkout — your domain, your styling, your back-button behavior — talk to us about the embedded checkout option.
