Venezuela: POS Mercantil C2P and Vuelto Digital

C2P Mobile Payment Integration and Vuelto Digital Banco Mercantil in Odoo 19 POS

Module functionalities

• Collection from the customer via interbank Mobile Payment
• Capture of phone, bank and payer's ID
• OTP requested from the issuing bank (Tpago for Mercantil)
• Reference and trace persistence in pos.payment
• Handling of 17 official error codes in Spanish
• Automatic calculation of change when receiving more than collected
• Sending via Mobile Payment to the customer's phone
• Receiver pre-loaded with data from step 1
• Editable if the recipient is different from the payer
• Separate collection reference for reconciliation
• Complete official list of the Mobile Payment system
• BDV, Mercantil, Provincial, Banesco, BNC, Tesoro…
• Selector with code + bank name
• Bank-Specific OTP Instructions
• SMS / bank app / Tpago depending on the issuer
• AES/ECB/PKCS5Padding with SHA-256 (16 bytes)
• Always encrypted in backend, never in JS
• Secret Key restricted to base.group_system
• Logs without sensitive data (ID, OTP, telephone)
• Strict TLS (verify=True) towards the bank
• Certification endpoint configurable by method
• Preloaded production endpoint
• Test Connection Button with SSL Verification
• Change mode without server restart
• Configurable timeout (default 30 s)
• Visual flow progress indicator
• Telephone validation (11 digits, 04XX format)
• ID/RIF validation (V/E/J + number)
• Pre-load ticket partner data
• Guided retries from the error screen
• Register at apiportal.mercantilbanco.com and subscribe to the "Mobile Payments Button (C2P) and Return" plan.
• Upon receiving the email from Mercantil with X-IBM-Client-Id, Secret Key, MerchantId and certification endpoint, go to Point of Sale Configuration Payment Methods.
• Edit the “C2P Mobile Payment (Mercantile)” method and upload the credentials to the C2P Merchant tab.
• Select Certification mode for testing and verify connectivity with the Test Connection button.
• Associate the payment method to the POS from the store settings.
• The cashier creates the ticket and selects "C2P Mobile Payment (Mercantile)" on the payment screen.
• The popup captures the customer's telephone number, issuing bank and ID/RIF (step 1).
• The customer gives the OTP to the cashier, who enters it and confirms the payment (step 2).
• The backend encrypts the sensitive data, calls the Mercantile API and displays the response (step 3).
• If the customer paid more than the amount charged, the popup calculates the change and offers to send it via Mobile Payment.
• The receiver is pre-loaded with the client's data; the cashier can change them if the destination is different.
• Upon confirmation, the bank generates the P2P transaction and returns the change reference.
• The final screen shows both references (collection + return) to print or deliver to the client.
• Inherits pos.payment.method, pos.payment and pos.order.
• Implement a custom PaymentInterface (PaymentMercantilC2P) in the POS, with native 5-step OWL2 popup.
• Official endpoint: POST https://apimbu.mercantilbanco.com/mercantil-banco/prod/v1/payment/c2p.
• X-IBM-Client-Id and JSON authentication header with merchant_identify, client_identify and transaction_c2p.
• Internal JSON-RPC endpoints: /web/pos/mercantil/c2p/{pay,vuelto,request_otp,banks,search}.
• Compatible with Odoo Enterprise and Community Edition.
• Depends on: point_of_sale, base_setup and the Python package pycryptodome.
• Point of Sale (point_of_sale)
• Initial Configuration (base_setup)
• pycryptodome (AES encryption)
• Legal account at Banco Mercantil
• Affiliation to the C2P service (generates the merchantId)
• Registration as a developer in the Mercantil API portal
• "Mobile Payments Button (C2P) and Return" Plan activated
• Valid SSL certificate on Odoo server

On screen

Specs

What is included with Mi-ERP