PEP & FEP Documentation
During onboarding, Manteca automatically checks whether a user is classified as a Politically Exposed Person (PEP) or a Fiscally Exposed Person (FEP) — also known as a UIF obligated subject. When a user is flagged, additional documentation is required before they can reach ACTIVE status.
Which flow applies
The detection is identical across products — the same screening, the same two onboarding tasks — but what you upload differs, so start from the product you integrate against:
| Product | What satisfies the task | Where to upload |
|---|---|---|
Crypto / RAMPS (/crypto/v2) | A PEP sworn declaration for the PEP task, and UIF documentation for the FEP task — one document per task. | The /crypto/v2 endpoints described on the rest of this page. |
Virtual Accounts (/wallet/v1) | A single proof of source of funds, for both tasks. | Either of the two /wallet/v1 endpoints — see Virtual Accounts: proof of source of funds. |
Everything from How it works down to After uploading describes the crypto flow. The Virtual Accounts rule is a section of its own further down.
How it works
flowchart LR
A[User created] -->|Auto-check| B{PEP/FEP?}
B -->|No| C[Continue onboarding]
B -->|PEP| D[PEP task required]
B -->|FEP| E[FEP task required]
D --> F[Upload PEP docs]
E --> G[Upload FEP docs]
F --> H[Validation]
G --> H
H -->|Approved| C
H -->|Rejected| I[Resubmit]
- Automatic detection — When a user is created, the
POLITICAL_CONSTRAINTS_VALIDATIONtask runs automatically. This checks the user's identity against regulatory databases. - Task assignment — If the user is flagged as PEP, the
PEP_DOCUMENTATION_VALIDATIONtask becomes required. If flagged as FEP (UIF obligated subject), theFEP_DOCUMENTATION_VALIDATIONtask becomes required. A user can be flagged as both. - Document upload — You must upload the required documentation using the corresponding endpoint.
- Validation — Manteca reviews the uploaded documentation. A
USER_ONBOARDING_UPDATEwebhook fires when the task is approved or rejected.
Detecting PEP/FEP flags
Via webhook
Listen for USER_ONBOARDING_UPDATE where updatedTasks includes POLITICAL_CONSTRAINTS_VALIDATION. After this task completes, check whether PEP_DOCUMENTATION_VALIDATION or FEP_DOCUMENTATION_VALIDATION changed to required: true. Both tasks are always present in the onboarding object — they start as required: false and only the required flag flips when the user is flagged:
{
"event": "USER_ONBOARDING_UPDATE",
"data": {
"user": {
"status": "ONBOARDING",
"onboarding": {
"POLITICAL_CONSTRAINTS_VALIDATION": {
"required": true,
"status": "COMPLETED"
},
"PEP_DOCUMENTATION_VALIDATION": {
"required": true,
"status": "PENDING"
},
"FEP_DOCUMENTATION_VALIDATION": {
"required": false,
"status": "PENDING"
}
}
},
"updatedTasks": ["POLITICAL_CONSTRAINTS_VALIDATION"]
}
}Via API
Call GET /v2/users/:userAnyId and inspect the onboarding tasks. If PEP_DOCUMENTATION_VALIDATION or FEP_DOCUMENTATION_VALIDATION shows required: true with status: "PENDING", the user needs to upload documentation. Evaluate this only after POLITICAL_CONSTRAINTS_VALIDATION reaches COMPLETED — before that, the check has not run and required may still be false.
What is PEP?
A Politically Exposed Person is someone who holds or has held a prominent public function — such as heads of state, senior politicians, judicial officials, or military officers. Immediate family members and close associates may also be classified as PEP.
What to upload: A sworn declaration of assets and income, or any document that justifies the user's source of funds — the same evidence described in what counts as proof of source of funds.
What is FEP?
A Fiscally Exposed Person (also called UIF obligated subject) is someone who is required to report to Argentina's Financial Information Unit (UIF) — such as accountants, notaries, real estate brokers, or financial intermediaries.
What to upload: Documentation certifying the user's UIF registration or a declaration of compliance with reporting obligations.
Uploading PEP documentation
Use POST /v2/onboarding-actions/upload-pep-documentation to get a presigned upload URL, then upload the file to that URL.
# Step 1 – Get upload URL
curl --request POST \
--url 'https://sandbox.manteca.dev/crypto/v2/onboarding-actions/upload-pep-documentation' \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--header 'md-api-key: YOUR_MD_API_KEY' \
--data '{
"userAnyId": "100037161",
"fileName": "pep-declaration.pdf"
}'
# Step 2 – Upload file to signed URL (no md-api-key header)
curl --request PUT \
--url 'SIGNED_URL_FROM_STEP_1' \
--header 'Content-Type: application/pdf' \
--data-binary '@/path/to/pep-declaration.pdf'Uploading FEP documentation
Use POST /v2/onboarding-actions/upload-fep-documentation with the same two-step flow.
# Step 1 – Get upload URL
curl --request POST \
--url 'https://sandbox.manteca.dev/crypto/v2/onboarding-actions/upload-fep-documentation' \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--header 'md-api-key: YOUR_MD_API_KEY' \
--data '{
"userAnyId": "100037161",
"fileName": "uif-compliance-certificate.pdf"
}'
# Step 2 – Upload file to signed URL (no md-api-key header)
curl --request PUT \
--url 'SIGNED_URL_FROM_STEP_1' \
--header 'Content-Type: application/pdf' \
--data-binary '@/path/to/uif-compliance-certificate.pdf'After uploading
Once the documentation is uploaded, Manteca reviews it. The typical outcomes are:
| Task status | Meaning | Next steps |
|---|---|---|
IN_PROGRESS | Documentation is being reviewed | Wait for the webhook |
COMPLETED | Documentation approved | User continues onboarding |
FAILED | Documentation rejected | Check rejectionReason and resubmit |
PEP/FEP documentation review may take longer than automatic tasks like identity declaration. The review is performed by Manteca's compliance team.
Virtual Accounts: proof of source of funds
In the Virtual Accounts product (/wallet/v1) an individual flagged as PEP, as FEP, or as both submits one document: proof of the source of their funds. It is the same document in either case — there is no separate PEP declaration and no separate UIF certificate.
Two ways in, one outcome
The document can be uploaded through either endpoint, and the choice changes nothing about the result:
| Endpoint | Body |
|---|---|
POST /wallet/v1/onboarding-actions/upload-pep-documentation | userAnyId, fileName |
POST /wallet/v1/onboarding-actions/upload-fep-documentation | userAnyId, fileName |
Both are two-step uploads: the call returns a 90-second pre-signed S3 url, and you PUT the raw file binary to it without the md-api-key header.
Once compliance approves the document, every one of PEP_DOCUMENTATION_VALIDATION and FEP_DOCUMENTATION_VALIDATION that is required moves to COMPLETED. A user flagged as both uploads a single file — not one per task, and not one per endpoint.
What counts as proof of source of funds
The document has to show where the person's money comes from, carry their name, and state an amount and the period it covers. Any of these works:
- The person's last three payslips.
- Their most recent income tax return.
- A statement of income issued and signed by a certified accountant.
- Evidence of a specific inflow — the sale of a property or of securities, or a loan received.
These are not accepted on their own, because they identify the person or their tax status without evidencing income:
- An identity document.
- A bank statement.
- A certificate of tax registration.
Send one file per upload. If the evidence spans several documents — three payslips, for instance — merge them into a single file first: a partial upload is reviewed as what it is and rejected.
The list is deliberately generic. Local equivalents of these documents are accepted, and if you are unsure whether a specific one qualifies in your market, ask your integration contact before the user uploads it.
An approved document already on file counts
The rule is about the document, not about when it arrived. If the user already has an approved proof of source of funds when the screening flags them, the task is COMPLETED as soon as it becomes required, and you upload nothing.
Read the task status before you prompt the user for a file: a flagged user is not necessarily a user who owes you a document.
Companies
A company flagged as PEP is covered by the corporate documents its onboarding already requires — the articles of incorporation (ESTATUTO) or the financial statement (BALANCE), either one. Proof of source of funds is the individual document and does not satisfy a company's PEP task. A company flagged as FEP uploads its AML/KYC policy through the FEP endpoint, against the company userAnyId. See Creating a virtual account for a company.
Shareholders and legal representatives are individuals with onboarding of their own, so the individual rule above applies to them, against their own userAnyId.
Frequently asked questions
Does PEP/FEP block the user from operating?
Yes. While a required PEP_DOCUMENTATION_VALIDATION or FEP_DOCUMENTATION_VALIDATION is PENDING or IN_PROGRESS, the user remains in ONBOARDING status and cannot operate.
Can one document close both the PEP and the FEP task?
In Virtual Accounts, yes — a single proof of source of funds completes both, since it is the document each of them asks for. In the crypto flow they stay separate: the PEP task takes the sworn declaration and the FEP task takes the UIF documentation.
Are PEP/FEP checks country-specific?
PEP checks apply to all countries. The FEP concept originates from Argentina's UIF (obligated subjects), but the FEP_DOCUMENTATION_VALIDATION task can be raised for a user of any country if the screening flags them as FEP.
Can a user be flagged after activation?
Yes — by a later screening, by the user's own declaration, or by Manteca's compliance team. The matching documentation task turns required: true and you receive a USER_ONBOARDING_UPDATE, the same one described in Via webhook. Upload the documentation as you would during onboarding.
When an ACTIVE individual is flagged as PEP, their status moves to INACTIVE while PEP_DOCUMENTATION_VALIDATION is pending, and returns to ACTIVE on its own once the documentation is approved — no action from Manteca needed. If an approved document is already on file, the user stays ACTIVE. Companies are not deactivated by a PEP flag.
How do I know if the PEP check is still running?
The POLITICAL_CONSTRAINTS_VALIDATION task will show status: "PENDING" or IN_PROGRESS. Wait for the webhook — do not upload PEP/FEP docs before this task completes, as the user may not be flagged.
Related pages
Updated 19 days ago