KYC - ARS (Fiat)
To operate ARS fiat (Argentine Peso) with Avenia, the user must complete ARS KYC in addition to standard identity verification.
KYC Level 1 must be completed and approved before you can request ARS KYC. Complete Level 1 first using the KYC Level 1 guide.
You can request ARS KYC from the Avenia dashboard or via the API described below.
The status lifecycle of an ARS KYC attempt is the same as for KYC Level 1 (for example PENDING, PROCESSING, COMPLETED, with result APPROVED or REJECTED). Track progress with List All KYC Attempts and Get KYC Attempt by ID in the KYC Level 1 guide. If webhooks are enabled for your account, you will receive the same KYC event types as for other KYC flows.
ARS KYC is processed through Avenia's ARS fiat rail. When approval completes, the user's ARS rail is unlocked and they can create ARS payins / payouts via the Operations endpoints.
Request ARS KYC via API
Use this endpoint to start an ARS KYC request programmatically. No request body is required.
HTTP POST Request
https://api.sandbox.avenia.io:10952/v2/kyc/ars/api
Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
subAccountId | string | No | When requesting ARS KYC for a subaccount, pass the subaccount ID as a query parameter. |
cURL Example (main account)
curl -X POST "https://api.sandbox.avenia.io:10952/v2/kyc/ars/api" \
-H "Authorization: Bearer eyJhdXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
cURL Example (subaccount)
curl -X POST "https://api.sandbox.avenia.io:10952/v2/kyc/ars/api?subAccountId=1ee0a663-922b-4389-9f84-074ccff7085d" \
-H "Authorization: Bearer eyJhdXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
For subaccounts, the same subAccountId query parameter pattern applies when listing or fetching KYC attempts for that user.
Response
201 Created with a JSON body identifying the KYC attempt. Poll the attempt via the Level 1 endpoints to watch the status transition to COMPLETED / APPROVED.
Scenarios
The endpoint is idempotent per user and adapts to the current fiat-rail KYC state:
| Current state for this user | What happens on POST /v2/kyc/ars/api |
|---|---|
| No fiat-rail KYC yet | A new fiat-rail profile is created, your Level 1 KYC documents are submitted, and a new KYC attempt is returned. You will receive KYC-STARTED → KYC-PROCESSING → KYC-COMPLETED webhooks. |
Fiat-rail KYC already approved (e.g. user previously passed for COP or MXN) | Skips the re-verification round-trip, enables the ARS rail immediately, and emits the full KYC-STARTED → KYC-PROCESSING → KYC-COMPLETED (APPROVED) webhook lifecycle so the client experience is identical. |
Fiat-rail KYC pending (still awaiting verification) | Registers the ARS currency as part of the in-flight workflow and returns the attempt ID. Approval webhooks fire when verification finishes. |
Related documentation
- KYC Level 1 — document upload, selfie / liveness, Web SDK, and shared KYC attempt APIs
- Operations — ARS to Crypto / Crypto to ARS — what the user can do once ARS KYC is approved
- Beneficiary Bank Accounts — ARS — required to receive ARS via payout
- Webhook events — KYC subscription and event types