|
2 | 2 | Authorize.Net |
3 | 3 | ============= |
4 | 4 |
|
5 | | -`Authorize.Net <https://www.authorize.net>`__ is a United States-based online payment solution |
6 | | -provider, allowing businesses to accept **credit cards**. |
7 | | - |
8 | | -.. image:: authorize/authorize-net.png |
9 | | - :align: center |
10 | | - :alt: Authorize.Net logo |
11 | | - |
12 | | -This Payment Acquirer offers additional options that are not available for other :doc:`Payment |
13 | | -Acquirers <../payment_acquirers>`, such as the ability to process your customer's payment after |
14 | | -delivery. |
| 5 | +`Authorize.Net <https://www.authorize.net>`_ is a United States-based online payment solution |
| 6 | +provider allowing businesses to accept **credit cards**. Among others, it offers the ability to |
| 7 | +process customer payments after delivery. |
15 | 8 |
|
16 | 9 | Authorize.Net account |
17 | 10 | ===================== |
18 | 11 |
|
19 | | -If not done yet, choose a plan and `Sign Up for an Authorize.Net account |
20 | | -<https://www.authorize.net/sign-up.html>`__. |
| 12 | +First, choose a plan and `create an Authorize.Net account |
| 13 | +<https://www.authorize.net/sign-up/pricing.html>`_. |
| 14 | + |
| 15 | +Odoo needs the Authorize.Net account's **API credentials and keys** to connect to it, which |
| 16 | +comprises the: |
21 | 17 |
|
22 | | -Odoo needs your **API Credentials & Keys** to connect with your Authorize.Net account, which |
23 | | -comprise: |
| 18 | +- API login ID, |
| 19 | +- Transaction key, and |
| 20 | +- Signature key. |
24 | 21 |
|
25 | | -- API Login ID |
26 | | -- Transaction Key |
27 | | -- Signature Key |
| 22 | +To retrieve them, log in to Authorize.Net and go to :menuselection:`Account --> Security Settings: |
| 23 | +API Credentials & Keys`. While the :guilabel:`API Login ID` is displayed, both keys need to be |
| 24 | +generated. |
28 | 25 |
|
29 | | -To retrieve them, log into your Authorize.Net account, go to :menuselection:`Account --> Security |
30 | | -Settings --> General Security Settings --> API Credentials & Keys`, and generate your **Transaction |
31 | | -Key** and **Signature Key**. |
| 26 | +To do so, select :guilabel:`New Transaction Key` and click :guilabel:`Submit`. Copy the key and |
| 27 | +store it somewhere secure as it will not be displayed afterward. Repeat the same process for the |
| 28 | +:guilabel:`Signature Key`. |
32 | 29 |
|
33 | 30 | .. image:: authorize/authorize-api-keys.png |
34 | | - :align: center |
35 | | - :alt: Generate your Transaction Key and Signature Key on your Authorize.Net account |
| 31 | + :alt: Generating the transaction and signature keys on Authorize.Net |
36 | 32 |
|
37 | 33 | .. seealso:: |
| 34 | + `Authorize.Net Getting Started Guide |
| 35 | + <https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000002939>`_ |
38 | 36 |
|
39 | | - - `Authorize.Net: Getting Started Guide |
40 | | - <https://support.authorize.net/s/article/Authorize-Net-Getting-Started-Guide>`__ |
41 | | - |
42 | | -Payment Acquirer Configuration |
43 | | -============================== |
| 37 | +Configuration |
| 38 | +============= |
44 | 39 |
|
45 | | -To configure Authorize.Net as Payment Acquirer in Odoo, go to :menuselection:`Accounting --> |
46 | | -Configuration --> Payment Acquirers`, open **Authorize.Net**, and change the **State** to *Enabled*. |
47 | | -Don't forget to click on *Save* once you've set everything up. |
| 40 | +.. seealso:: |
| 41 | + Refer to the :doc:`payment acquirers documentation <../payment_acquirers>` for more information |
| 42 | + about general configuration options. |
48 | 43 |
|
49 | | -.. note:: |
50 | | - Please refer to the :doc:`Payment Acquirers documentation <../payment_acquirers>` to read how to |
51 | | - configure this payment acquirer. |
| 44 | +To activate Authorize.Net as a payment acquirer in Odoo, go to :menuselection:`Accounting --> |
| 45 | +Configuration --> Payment Acquirers`. Find :guilabel:`Authorize.Net`, click the :guilabel:`Activate` |
| 46 | +button, and change the :guilabel:`State` to :guilabel:`Enabled`. |
52 | 47 |
|
53 | 48 | Credentials |
54 | 49 | ----------- |
55 | 50 |
|
56 | | -Copy your credentials from your Authorize.Net account (API Login Id, API Transaction Key, and API |
57 | | -Signature Key), paste them in the related fields under the **Credentials** tab, then click on |
58 | | -**Generate Client Key**. |
| 51 | +Fill in the :guilabel:`API Login Id`, :guilabel:`API Transaction Key`, and :guilabel:`API Signature |
| 52 | +Key` fields with the values displayed or generated on Authorize.Net's :guilabel:`API Credentials & |
| 53 | +Keys` page, and :guilabel:`Save`. |
59 | 54 |
|
60 | 55 | .. note:: |
61 | | - The **API Client Key** is necessary only if you select *Payment from Odoo* option as |
62 | | - :ref:`Payment Flow <payment_acquirers/payment_flow>`. |
| 56 | + An :guilabel:`API Client Key` is only necessary if the :guilabel:`Payment from Odoo` option is |
| 57 | + selected as :ref:`Payment Flow <payment_acquirers/payment_flow>`. |
63 | 58 |
|
64 | 59 | .. important:: |
65 | | - If you are trying Authorize.Net as a test, with a *sandbox account*, change the :guilabel:`State` |
66 | | - to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, rather than on your |
67 | | - main database. |
| 60 | + To test Authorize.Net with a **sandbox account**, first change the :guilabel:`State` field to |
| 61 | + :guilabel:`Test Mode`. It is recommended to do so on a test Odoo database, rather than on a |
| 62 | + production database. |
68 | 63 |
|
69 | | - If you set :guilabel:`Test Mode` on Odoo and use an authorize.net account instead of a |
70 | | - sandbox.authorize.net account, it results in the following error: *The merchant login ID or |
71 | | - password is invalid or the account is inactive*. |
| 64 | + .. note:: |
| 65 | + If the :guilabel:`Test Mode` is used with the credentials of a non-sandbox account, it will |
| 66 | + result in the following error: *The merchant login ID or password is invalid or the account is |
| 67 | + inactive*. |
72 | 68 |
|
73 | | -Payment Flow |
| 69 | +Payment flow |
74 | 70 | ------------ |
75 | 71 |
|
76 | | -The **Payment Flow** lets you decide if to redirect the user to the payment acquirer's portal to |
77 | | -authenticate the payment, or if to stay on the current page and authenticate the payment from Odoo. |
78 | | -This field is under the **Configuration** tab. |
| 72 | +It is possible either to redirect users to Authorize.Net's portal to authenticate the payment or to |
| 73 | +keep users on the current page and authenticate the payment from Odoo. |
79 | 74 |
|
80 | | -If you select *Redirection to the acquirer website*, make sure you add a **Default Receipt URL** and |
81 | | -a **Default Relay Response URL** to your Authorize.net account. |
| 75 | +To configure the payment flow, go to :menuselection:`Accounting --> Configuration --> Payment |
| 76 | +Acquirers --> Authorize.Net --> Configuration tab`. Under :guilabel:`Payment Flow`, select |
| 77 | +:guilabel:`Redirection to the acquirer website` or :guilabel:`Payment from Odoo` and |
| 78 | +:guilabel:`Save`. |
82 | 79 |
|
83 | | -To do so, log into your Authorize.Net account, go to :menuselection:`Account --> Transaction Format |
84 | | -Settings --> Transaction Response Settings --> Response/Receipt URLs`, and set the default links: |
| 80 | +Payment from Odoo |
| 81 | +~~~~~~~~~~~~~~~~~ |
85 | 82 |
|
86 | | -- | Default Receipt URL: |
87 | | - | *https://[yourcompany.odoo.com]*/**payment/authorize/return** |
88 | | -- | Default Relay Response URL: |
89 | | - | *https://[yourcompany.odoo.com]*/**shop/confirmation** |
| 83 | +If :guilabel:`Payment from Odoo` is selected, an :guilabel:`API Client Key` is needed. To generate |
| 84 | +one, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers --> Authorize.Net --> |
| 85 | +Credentials tab`. Click :guilabel:`Generate Client Key` to automatically fill in the :guilabel:`API |
| 86 | +Client Key` field and :guilabel:`Save`. |
90 | 87 |
|
91 | | -.. note:: |
92 | | - | Failing to complete this step results in the following error: |
93 | | - | *The referrer, relay response or receipt link URL is invalid.* |
| 88 | +Redirection to the acquirer website |
| 89 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
94 | 90 |
|
95 | | -Capture the payment after the delivery |
96 | | --------------------------------------- |
| 91 | +If :guilabel:`Redirection to the acquirer website` is selected, a :guilabel:`Default Receipt URL` |
| 92 | +and :guilabel:`Default Relay Response URL` should be added to the Authorize.Net account. |
97 | 93 |
|
98 | | -The **Capture Amount Manually** field is under the **Configuration** tab. If enabled, the funds are |
99 | | -reserved for 30 days on the customer's card, but not charged yet. |
| 94 | +To do so, log in to Authorize.Net, and go to :menuselection:`Account --> Transaction Format |
| 95 | +Settings: Response/Receipt URLs`. Click :guilabel:`Add URL`, enter the URL following the format |
| 96 | +below, and click :guilabel:`Submit`: |
100 | 97 |
|
101 | | -.. image:: authorize/authorize-configuration.png |
102 | | - :align: center |
103 | | - :alt: Authorize.Net Configuration tab on Odoo |
| 98 | +- :guilabel:`Default Receipt URL`: add `/payment/authorize/return` after the main website URL. |
104 | 99 |
|
105 | | -To capture the payment, go to the related Sales Order and click on *Capture Transaction*. If the |
106 | | -order is canceled, you can click on *Void Transaction* to unlock the funds from the customer's card. |
| 100 | + .. example:: |
| 101 | + `https://example.odoo.com/payment/authorize/return` |
107 | 102 |
|
108 | | -.. image:: authorize/authorize-capture.png |
109 | | - :align: center |
110 | | - :alt: Hold the credit card payment until you capture or revoke it on Odoo |
| 103 | +- :guilabel:`Default Relay Response URL`: add `/shop/confirmation` after the main website URL. |
111 | 104 |
|
112 | | -.. warning:: |
113 | | - After **30 days**, the transaction is **voided automatically** by Authorize.net. |
| 105 | + .. example:: |
| 106 | + `https://example.odoo.com/shop/confirmation` |
| 107 | + |
| 108 | +.. image:: authorize/authorize-redirect-urls.png |
| 109 | + :alt: Adding the response and receipt URLs on Authorize.Net |
114 | 110 |
|
115 | 111 | .. note:: |
116 | | - With other payment acquirers, you can manage the capture in their own interfaces, not from Odoo. |
| 112 | + Failing to complete this step results in the following error: *The referrer, relay response or |
| 113 | + receipt link URL is invalid*. |
| 114 | + |
| 115 | +Capture payments after delivery |
| 116 | +------------------------------- |
| 117 | + |
| 118 | +To reserve funds for 30 days on the customer's card without charging them yet, go to |
| 119 | +:menuselection:`Accounting --> Configuration --> Payment Acquirers --> Authorize.Net --> |
| 120 | +Configuration tab`, enable :guilabel:`Capture Amount Manually`, and :guilabel:`Save`. |
| 121 | + |
| 122 | +To capture the payment, go to the related sales order and click :guilabel:`Capture Transaction`. If |
| 123 | +the order is canceled, click :guilabel:`Void Transaction` to unlock the funds from the customer's |
| 124 | +card. |
| 125 | + |
| 126 | +.. image:: authorize/authorize-capture.png |
| 127 | + :alt: Capturing the payment manually |
| 128 | + |
| 129 | +.. warning:: |
| 130 | + After **30 days**, transactions are **voided automatically** by Authorize.Net. |
117 | 131 |
|
118 | 132 | .. seealso:: |
119 | 133 | - `Authorize.Net: Getting Started Guide |
120 | | - <https://support.authorize.net/s/article/Authorize-Net-Getting-Started-Guide>`__ |
| 134 | + <https://support.authorize.net/s/article/Authorize-Net-Getting-Started-Guide>`_ |
121 | 135 | - :doc:`../payment_acquirers` |
122 | 136 | - :doc:`../../websites/ecommerce/shopper_experience/payment_acquirer` |
0 commit comments