| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Invoicing (account) • Discuss (mail) • Website (website) |
| Community Apps Dependencies | Show |
| Lines of code | 1638 |
| Technical Name |
payment_authorize_backend |
| License | OPL-1 |
| Website | http://www.sodexis.com |
| Versions | 10.0 11.0 12.0 13.0 14.0 15.0 16.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Invoicing (account) • Discuss (mail) • Website (website) |
| Community Apps Dependencies | Show |
| Lines of code | 1638 |
| Technical Name |
payment_authorize_backend |
| License | OPL-1 |
| Website | http://www.sodexis.com |
| Versions | 10.0 11.0 12.0 13.0 14.0 15.0 16.0 |
Payment Authorize.net Backend
Provides Authorize.net API for credit card payments in Odoo backend.
Description
This module extends the functionality of Odoo v13 to support website payment integration.
And adds the facility to add payment token for a customer via an Odoo user.
The payment token/credit cards can be created from Contacts, Sales order and Account Invoice form view.
Configuration
Add Authorize.net as a payment acquirer in Test Mode
- - In Accounting application for Sales orders
- - In Website application for Online Sales
Enter:
- API Login Id
- API Transaction Key
- API Signature Key
- API Client Key
Create Authorize.net Journal
Functionality
Cards can be added directly to the customer contact at any time, Sales order upon
confirmation, or invoice to register payment.
To add a card on a contact, use the "Add a card" smart button on the top left (could also be in drop down). Set payment method on customer contact to Authorize.net is this is their default payment method.
To add a card on a contact, use the "Add a card" smart button on the top left (could also be in drop down). Set payment method on customer contact to Authorize.net is this is their default payment method.
Note: No credit card information is being stored in Odoo, only the payment token. All credit card information is stored in Authorize.net.
Lets see the screenshots for the overview of the module functionality.
Contact us by apps@sodexis.com or fill out request form
Payment Authorize.net Backend
Configuration
To configure this module follow the below steps.
- Go to Accounting -> Configuration -> Payment Acquirers -> Authorize.net and configure with your API login and transaction key and publish it.
- Create a Journal of type bank to use it Authorize.net transactions.
- In that Jounal Go to Advanced Settings.
- Under Miscellaneous Group choose the Debit method as Electronic.
- Choose Payment Acquirer as Authorize.net and leave Payment methods as unchecked.
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