apimbu.mercantilbanco.com) using the configured X-IBM-Client-ID. Sensitive fields (CVV, national ID, phone numbers) are AES-256 encrypted before transmission.
All request bodies use the data envelope.
api_mercantil_auth
api_mercantil_tdd_pay to obtain the twofactor_auth OTP challenge.
Forwards to: POST https://apimbu.mercantilbanco.com/mercantil-banco/prod/v1/payment/getauth
Request body
Cardholder national ID (cédula). Sent as-is (not encrypted at this step).
Debit card number.
Client IP address, forwarded to Mercantil for fraud detection.
Response
200 on success, 400 on Mercantil error.Raw response object from the Mercantil
getauth endpoint.Example
api_mercantil_tdd_pay
POST https://apimbu.mercantilbanco.com/mercantil-banco/prod/v1/payment/pay with payment_method: "tdd"
Request body
Transaction amount in VES (bolívares).
Unique invoice/order number for idempotency.
Cardholder national ID (cédula).
Debit card number.
Card verification value. Encrypted with AES-256 before sending to Mercantil.
Card expiration date in the format accepted by Mercantil (e.g.
"MM/YY").Mercantil account type code (e.g.
"CC" for current, "CA" for savings).OTP/two-factor code obtained from
api_mercantil_auth. Encrypted with AES-256 before sending.Client IP address.
Response
"Procesado" on success, "Error" on failure.Raw response object from the Mercantil payment endpoint.
Example
api_mercantil_tdc_pay
account_type or twofactor_auth is required.
Forwards to: POST https://apimbu.mercantilbanco.com/mercantil-banco/prod/v1/payment/pay with payment_method: "tdc"
Request body
Transaction amount in VES.
Unique invoice/order number.
Cardholder national ID (cédula).
Credit card number.
Card verification value. AES-256 encrypted before forwarding.
Card expiration date.
Client IP address.
Response
"Procesado" on success, "Error" on failure.Raw response object from the Mercantil payment endpoint.
Example
api_mercantil_c2p_auth
destination_id and destination_mobile_number are AES-256 encrypted before forwarding. This call registers the merchant’s intent to charge a payer via mobile payment.
Forwards to: POST https://apimbu.mercantilbanco.com/mercantil-banco/sandbox/v1/mobile-payment/scp
Request body
National ID (cédula) of the payment destination (merchant). AES-256 encrypted before forwarding.
Merchant mobile phone number registered for Pago Móvil. AES-256 encrypted before forwarding.
Client IP address.
Response
"Procesado" on success, "Error" on failure.Raw response from the Mercantil SCP endpoint.
api_mercantil_c2p_pay
POST https://apimbu.mercantilbanco.com/mercantil-banco/prod/v1/payment/c2p
Request body
Transaction amount in VES.
Unique invoice/order number.
Bank code of the destination (merchant) bank, e.g.
"0105" for Mercantil.National ID of the payment destination. AES-256 encrypted before forwarding.
Destination (merchant) mobile number for Pago Móvil. AES-256 encrypted before forwarding.
Payer’s mobile number. AES-256 encrypted before forwarding.
A reference string provided by the payer’s bank to identify the transaction.
OTP code from the payer. AES-256 encrypted before forwarding.
Client IP address.
Response
"Procesado" on success, "Error" on failure.Raw response from the Mercantil C2P endpoint.
Example
api_mercantil_c2p_search
order_created.
Forwards to: POST https://apimbu.mercantilbanco.com/mercantil-banco/prod/v1/mobile-payment/search
Request body
Destination mobile number to search. AES-256 encrypted before forwarding.
Payer mobile number to search. AES-256 encrypted before forwarding.
Reference number to match.
Expected transaction amount in VES.
Transaction date to search, in the format accepted by Mercantil (e.g.
"YYYYMMDD").Client IP address.
Response
"Procesado" on success, "Error" on failure.Array of matching transaction objects from Mercantil’s
transaction_list.