Skip to content

Commit 5972296

Browse files
Apply suggestions from code review
One last Felicia review before merging Co-authored-by: Felicia Kuan <[email protected]>
1 parent bf2bdbd commit 5972296

File tree

1 file changed

+9
-10
lines changed

1 file changed

+9
-10
lines changed

content/applications/sales/subscriptions/automatic_payments.rst

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,21 +23,21 @@ account information, for automatic billing. The following payment providers supp
2323

2424
Here are the steps to setting up automatic payments.
2525

26-
1. Choose a payment provider that supports tokenization.
27-
2. Follow the provider's own setup guide to create an account and begin configuring their API
26+
#. Choose a payment provider that supports tokenization.
27+
#. Follow the provider's own setup guide to create an account and begin configuring their API
2828
credentials in Odoo.
29-
3. :ref:`Enable <payment_providers/add_new>` the payment provider.
30-
4. :ref:`Configure the payment methods <payment_providers/payment_methods>` for the chosen payment
29+
#. :ref:`Enable <payment_providers/add_new>` the payment provider.
30+
#. :ref:`Configure the payment methods <payment_providers/payment_methods>` for the chosen payment
3131
provider.
32-
5. :ref:`Configure the tokenization <payment_providers/tokenization>` for the chosen payment
32+
#. :ref:`Configure the tokenization <payment_providers/tokenization>` for the chosen payment
3333
provider.
3434

3535
How customers can set up automatic payments
3636
===========================================
3737

3838
Once these steps are complete, payment providers will be able to create tokens with customers' saved
3939
payment details during the checkout process. Saved payment details can then be used for future
40-
payments when making new online payments or paying the recurring costs of a subscription. Customers
40+
online or recurring subscription charges. Customers
4141
will also be able to log into their :doc:`customer portal <../../general/users/portal>` and enter
4242
their payment information there.
4343

@@ -52,10 +52,9 @@ payments.
5252
What happens if an automatic payment fails?
5353
===========================================
5454

55-
On rare occasions, automatic payments can fail to register properly, which results in a
56-
:guilabel:`Payment Failure` tag on the sales order and the :guilabel:`Contract in exception`
57-
checkbox being automatically ticked in the :guilabel:`Subscription` section of the sales order's
58-
:guilabel:`Other Info` tab.
55+
When an automatic payment fails, the sales order is updated with
56+
- an :guilabel:`Payment Failure` tag
57+
- the :guilabel:`Contract in exception` checkbox ticked (in the :guilabel:`Subscription` section of the :guilabel:`Other Info` tab).
5958

6059
Being marked :guilabel:`Contract in exception` prevents scheduled actions from running, which keeps
6160
the system from accidentally double-charging the customer if the automatic payment actually went

0 commit comments

Comments
 (0)