Skip to main content
POST
Activate a Business Merchant Account
Use this endpoint to activate one or more fiat payment channels for a business (BUSINESS type) merchant. The process mirrors the individual activation flow, but business accounts typically require fewer personal fields and may instead require company registration data and UBO (Ultimate Beneficial Owner) information depending on the payment provider.
All requests must include the X-BH-TOKEN header and Content-Type: application/json.

Endpoint

POST https://api.velafi.com/v2/merchant/accounts

Core Request Fields

string
required
The ID of the business merchant to activate.
string
required
Target fiat currency. Supported values: MXN, ARS, COP, BRL, PEN, EUR, USD.
string
required
Payment provider or account type identifier. Must match a supported value for the chosen fiat.
string
Redirect URL after the merchant accepts a compliance agreement. Used by Lead Bank channels; if you omit it, a VelaFi default redirect URL is used.
object
Channel-specific fields. Content varies by fiat and trench. See per-currency examples below.

Response Fields

number
HTTP-style response code. 200 indicates success.
string
Human-readable status message, e.g. SUCCESS.
object

How Business Activation Works

A business activation takes one of two paths. The response tells you which one applied. Additional business verification (status: 0 with a verifyLink). For a business merchant, the local channels for MXN (CLABE - FINCO PAY, CLABE - TESORED), COP (COP Account), ARS (CVU - Momentum, QR Argentina), BRL (BANCO GENIAL) and PEN (PEN Account) normally require an additional KYB verification for that channel. The response returns status: 0 and a verifyLink. Send the business to the link to complete the verification. After VelaFi approves it, the channel is opened automatically, so you do not need to call this endpoint again. On this path, the fieldList in your request is not used. Direct activation. If VelaFi has enabled direct activation for your account, the channel is opened from your request and fieldList must contain the channel’s required fields. A missing or invalid field rejects the request.

Examples by Currency

MXN — SPEI via Finco Pay (trench: "CLABE - FINCO PAY")
Request body
MXN — SPEI via Tesored (trench: "CLABE - TESORED")
Request body

Response Examples

Business BRL Woovi activations require complete companyInfo and 1 to 50 entries in companyUbosInfo. The document fields (certificateOfIncorporationDocumentUrl, taxIdentificationDocumentUrl and each UBO’s govIdFrontUrl) must be fileUrl values returned by Upload File. Public URLs are rejected. Missing or invalid fields cause the activation to fail immediately.