| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• eCommerce (website_sale) • Discuss (mail) • Website (website) |
| Community Apps Dependencies | Show |
| Lines of code | 2636 |
| Technical Name |
payment_authorize_backend |
| License | OPL-1 |
| Website | https://sodexis.com/ |
| Versions | 11.0 12.0 13.0 10.0 15.0 16.0 14.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• eCommerce (website_sale) • Discuss (mail) • Website (website) |
| Community Apps Dependencies | Show |
| Lines of code | 2636 |
| Technical Name |
payment_authorize_backend |
| License | OPL-1 |
| Website | https://sodexis.com/ |
| Versions | 11.0 12.0 13.0 10.0 15.0 16.0 14.0 |
Payment Authorize Backend
Description
This module is configured to connect the backend of Odoo to the Authorize.net and enables the addition of a credit card or saved payment token to sales orders, customer contacts, and invoices.
Configuration
Go To Accounting - - > Configuration - - > Payment Providers - - > Authorize.net.
Enter the credentials for Authorize.net under Credentials Tab.
Functionality
At any time, cards can be added directly to the client contact, a sales order after confirmation, or an invoice after registration of payment.
Use the “Add a card” smart button on the top left (which could alternatively be in the drop down) to add a card to a contact.
Set the customer's preferred payment method on their contact form for Authorize.net.
No credit card information is being stored in Odoo, only the payment token. All credit card information is stored in Authorize.net.
Select the Payment Journal and type of transaction in Confirmation of Sales order.
Click on the Internal Link of the “Authorize.Net” Payment Journal and add the Payment Method and Payment Provider under Incoming Payments tab.
Add the Allowed accounts under Advanced Settings tab.
Go to Contacts. Set the Sale Payment Method as “Authorize.Net” under Sales & Purchase tab of the contact and also add card details by clicking on “Add a card” in the contact form where the card information will be saved in “Saved payment token”.
Go to Sales and create a sale order for that particular contact. The “Payment Method” and Saved payment token” fields will be propagated in the sales order form.
Once we register the payment for the invoice in the sale order, set the Journal as “Authorize.Net” which automatically fills the Payment Method and Saved payment token fields values for “Authorize.Net.
Click on “Payment” smart button where we can view the transaction details using Authorize.Net.
Credits
Contributors
- Sodexis <apps@sodexis.com>
This module is maintained by Sodexis.
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