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

# Beneficiaries and payment instructions

> Beneficiaries are the people and companies in Brazil that receive your payouts. LB Pay does not onboard them as its own customers. Instead, every payment instruction (Pix key) you register is screened before it can be used in a remittance.

## How to register

1. Send the beneficiary’s data: type (individual or company), CPF or CNPJ, name (or legal name), address, relationship type and at least one Pix key.
2. Each Pix key enters `SCREENING` and LB Pay screens it automatically.
3. You are notified with `beneficiary.status_changed` when each key is `APPROVED` or `REJECTED`.
4. To add or deactivate a Pix key later, update the beneficiary.

> [!NOTE]
>
> You can pay a beneficiary when the beneficiary is `ACTIVE` and the Pix key is `APPROVED`.

| Beneficiary status | Meaning |
| - | - |
| `ACTIVE` | Can receive |
| `BLOCKED` | Cannot receive |
| `INACTIVE` | Deactivated by you |

| Pix key status | Meaning |
| - | - |
| `SCREENING` | Being screened; cannot receive yet |
| `APPROVED` | Can receive |
| `REJECTED` | Did not pass screening. Reasons are not detailed. |
| `INACTIVE` | Deactivated; history is kept |

## What LB Pay checks

* Identity: the beneficiary’s CPF or CNPJ, full name (or legal name) and country are checked against sanctions and PEP lists.
* Pix key: the key must exist in the Pix directory before it is approved.

The first key of a new beneficiary goes through the full screening. Later keys for the same beneficiary get a lighter check focused on the new key. Changing identity data (name, document or address) triggers a new screening.

When the withdrawal is created, LB Pay checks again that the key exists. Just before the Pix, LB Pay confirms that the key holder’s document matches the beneficiary. If it does not, the Pix is not sent and the remittance goes to `FUNDS_HELD_BRL`.

## What stays with you

LB Pay screens the data you send; it does not verify the person behind it. You remain responsible for:

* verifying the identity of each end user before they send or receive through LB Pay;
* keeping your own identity records (documents, proof of address and, when applicable, source of funds), as required by your regulators;
* making sure the beneficiary data you submit matches what you collected;
* applying your own limits and risk tiers. LB Pay’s screening is a payment control, not a replacement for your customer due diligence.

If your regulatory regime requires LB Pay to take part in your customer review, contact LB Pay’s compliance team. These arrangements are agreed separately.

## Relationship with the sender

| Relationship type | Meaning | Relationship accepted in the remittance |
| - | - | - |
| `SELF_OWNED` | The beneficiary is the sender, receiving in their own account in Brazil | Only `SELF` |
| `THIRD_PARTY` | Another person or company | Any except `SELF` |

The detailed relationship with the sender (family, friend, employer…) is informed in each remittance, because a third-party beneficiary can receive from different senders.

> [!TIP]
>
> **What you do**
>
> * Register the beneficiary with address, relationship type and a Pix key that belongs to them.
> * Wait for the key to be `APPROVED` before creating a withdrawal.
> * Inform a relationship in the remittance that matches the beneficiary type.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.