File tree Expand file tree Collapse file tree 1 file changed +23
-0
lines changed
content/applications/finance/payment_providers Expand file tree Collapse file tree 1 file changed +23
-0
lines changed Original file line number Diff line number Diff line change @@ -34,6 +34,29 @@ Key**.
3434 If you use the :guilabel: `Test Mode ` with a regular account, it results in the following error:
3535 *The merchant login ID or password is invalid or the account is inactive *.
3636
37+ Webhook Configuration
38+ ---------------------
39+
40+ Webhooks allow Odoo to receive real-time notifications about payment status changes from
41+ Authorize.Net, ensuring payment statuses are always up to date even if customers don't return
42+ to your site after payment.
43+
44+ To configure webhooks:
45+
46+ #. :ref: `Navigate to the payment provider Authorize.Net <payment_providers/add_new >` and ensure
47+ the :guilabel: `State ` is set to :guilabel: `Enabled ` (or :guilabel: `Test Mode ` for testing).
48+ #. In the :guilabel: `Credentials ` tab, click on :guilabel: `Generate your webhook `.
49+ #. Odoo will automatically create and configure the webhook in your Authorize.Net account.
50+
51+ .. note ::
52+ The webhook is automatically configured with the correct URL and event types. You can verify
53+ the webhook was created by logging into your Authorize.Net account and going to
54+ :menuselection: `Account --> Webhooks `.
55+
56+ .. tip ::
57+ If you need to update the webhook (for example, after changing your domain), simply click
58+ :guilabel: `Generate your webhook ` again. Odoo will update the existing webhook configuration.
59+
3760Configuration tab
3861-----------------
3962
You can’t perform that action at this time.
0 commit comments