Backend Payment Acquirer: Braintree

by
Odoo

162.63

v 15.0 Third Party 6
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Sales (sale_management)
Invoicing (account)
Discuss (mail)
Lines of code 2290
Technical Name sync_payment_braintree
LicenseOPL-1
Websitehttps://www.synconics.com
Versions 12.0 16.0 15.0 17.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Sales (sale_management)
Invoicing (account)
Discuss (mail)
Lines of code 2290
Technical Name sync_payment_braintree
LicenseOPL-1
Websitehttps://www.synconics.com
Versions 12.0 16.0 15.0 17.0

Odoo Backend Integration with Braintree

Braintree, a division of PayPal payment acquirer, is a company based in Chicago that specializes in mobile and web payment systems for E-commerce companies. Braintree payment gateway is one of the most secure and reliable payment method.

This module allows merchants to accept payments done through credit card through their website and over an Internet Protocol connection.

Integration of Odoo with Braintree together creates a strong database which makes all payment processes easy just within a click, with less data entry.

Note: Customer's credit card details remains secure at Odoo side. We are not store any credit card number as per PCI Compliance

This module is compatible with

Key Features

    Do payment from Odoo to Braintree payment acquirer
    Multi-company and Multi-currency support ( here we have to define different payment methods as per each company)
    Customer can Add/Delete credit card token.
    Sale payment process using credit card details.
    In Sale, Supported the authorized full amount payment without capture.
    In Sale and Invoice, Refund partial/full payment process are done using credit cards.
    In Sales Order Void unsettled payment transaction from Braintree.

Braintree Configuration

From Braintree Merchant account users will generate public key, private key, merchant id and merchant account id.

Odoo Configuration

Menu Sequence - Invoice -> Configuration -> Payment Acquirer -> Braintree.
Merchants have to write related account credentials in Odoo as defined here.

Customer Information Management (CIM)

1) Link customer from Odoo to Braintree:
Menu Sequence - Sales / Orders / Customers
Under Braintree tab by clicking on "Link to Braintree" button, it Odoo will collect related customer details and send it to Braintree merchant account from Odoo and send it to Braintree.
after that related "Customer ID" and "Merchant ID" will be created at Braintree side.
Only one customer profile can be linked to Braintree side as per each company.
We can also update and delete customer profile at Braintree side by clicking on update and unlink icon from Odoo.
2) Credit Card Registration:
Under Invoicing tab add credit card details and send it to Braintree to create "Customer Payment ID".
Note: We do not store any of credit card details at Odoo side as per PCI Compliance.

Payment Transaction with Braintree

1) Payment with Braintree in sales order:
i) Authorize Transaction:
To do payment using Braintree in sales order, click on 'Confirm with braintree' button.
At the time of the transaction, we can use the tokenized credit card and select "Capture Manually" to transact without being captured.
Once the transaction will be authorized, we can capture or voided payment transaction from invoice and related payment reference will be appeared in invoice payment transaction.
Captured or paid invoice.
Done payment transaction.
Transaction is successfully created on Braintree side.
ii) Authorize & Capture Transaction:
At the time of authorize and capture transaction, we can use the tokenized credit card and disable "Capture Manually" to transact with being captured.
User's will also able to add partial as well as full payment amount at Odoo side.
Payment transaction is successfully created with amount partially paid.
Customer payment transaction is successfully created along with payment transaction reference.
Partial payment entries on related invoice at Odoo side.
Payment transaction details will be appear at Braintree side.
2) Payment with Braintree in invoice:
Form invoice click on 'Register Payment' button.
At time of transaction we can use tokenized credit card details.
Users will be not allowed to create a new credit card detail directly from here.
Once the transaction will be done, then payment transaction reference will be appeared in invoice and invoice will be proceed to 'Posted' stage.
Related transaction details will be appeared at Odoo side.
Payment transaction details will appeared on Braintree side.

Refund Transaction with Braintree

We can also refund payment amount from Odoo side.
At refund time we can select partial/ full refund amount .
After click on 'Refund' button, A refund payment transaction will be created at Braintree side and related reference will be appeared in payment transactions at Odoo side.
Refund Payment transaction details will appeared at Odoo side.
Refund transaction details will appear at Braintree side.

Void Unsettled Transaction with Braintree

Users allowed with full accounting rights can cancel or void unsettled payment transaction.
At void transaction we can click on "Void Transactions" button on sale orders.
After clicking on 'Void Transaction' button, An unsettled payment transaction will be canceled or voided from Braintree side.
Void Payment transaction details will be appeared at Odoo side along with stage.
Related payment details will be canceled from posted automatically.
Void transaction details will be appeared at Braintree side.
status = 'Voided'.
Suggested Products

Terms & Conditions

  • All the apps are to be purchased separately, for individual versions and individual edition.
  • One month free bug support period will be offered pertaining to any one server used, testing or live.
  • Synconics is not responsible for installation or updating of the module on any of your server.
  • If an error appears in our app due to other custom modules installed in your system or if Odoo base source code is not updated on your system, to make it compatible with your source code, we'll charge you for our efforts to resolve those errors and make the module compatible with your source code.
  • Please refer the document for configuration. If any support is needed for module configuration, installation, updating or any help is needed, it will be considered in paid support.
  • Please note that you are not allowed to distribute or resell this module after purchase.
  • This module is tested and working on Odoo vanilla with Ubuntu OS.
  • Support services will be provided from Monday to Friday, 10:30 AM to 7 PM IST (Indian Standard Time).
  • Support will not be provided during Indian public holidays or company holidays.
Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.