[IMP] finance,*: change of the term "acquirer" to "provider"
Changing the name of model payment.acquirer to payment.provider and everything that it touches. It is technically incorrect to use the term "acquirer" for systems that only provide a service of payment. After this commit the model payment.acquirer and everything related to it will be renamed to payment.provider. Task - 2842088 closes odoo/documentation#1981 Related: odoo/upgrade#3542 Related: odoo/odoo#90899 Related: odoo/enterprise#27131 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
@ -71,7 +71,7 @@ The neutralization includes:
|
||||
* Disabling outgoing emails by intercepting them with a mailcatcher. An
|
||||
:ref:`interface to view <odoosh-gettingstarted-branches-tabs-mails>` the emails sent by your
|
||||
database is provided. That way, you do not have to worry about sending test emails to your contacts.
|
||||
* Setting payment acquirers and shipping providers in test mode.
|
||||
* Setting payment providers and shipping providers in test mode.
|
||||
* Disabling IAP services
|
||||
|
||||
The latest database will be kept alive indefinitely, older ones from the same branch may get garbage collected
|
||||
|
@ -11,4 +11,4 @@ Finance
|
||||
finance/expenses
|
||||
finance/documents
|
||||
finance/sign
|
||||
finance/payment_acquirers
|
||||
finance/payment_providers
|
@ -176,7 +176,7 @@ Payment Method
|
||||
This menu helps you configure the payment methods with which your customers can pay you.
|
||||
|
||||
.. important::
|
||||
Configuring a *Payment Acquirer* with this tool also activates the *Invoice Online Payment*
|
||||
Configuring a *Payment Provider* with this tool also activates the *Invoice Online Payment*
|
||||
option automatically. With this, users can directly pay online, from their Customer Portal.
|
||||
|
||||
.. _invoicing-setup-sample:
|
||||
|
@ -56,10 +56,10 @@ SEPA Direct Debit as a Payment Method
|
||||
-------------------------------------
|
||||
|
||||
SEPA Direct Debit can be used as a payment method both on your **eCommerce** or on the **Customer
|
||||
Portal** by activating SDD as a **Payment Acquirer**. With this method, your customers can create
|
||||
Portal** by activating SDD as a **Payment Provider**. With this method, your customers can create
|
||||
and sign their mandates themselves.
|
||||
|
||||
To do so, go to :menuselection:`Accounting --> Configuration --> Payment Acquirers`, click on *SEPA
|
||||
To do so, go to :menuselection:`Accounting --> Configuration --> Payment Providers`, click on *SEPA
|
||||
Direct Debit*, and set it up according to your needs.
|
||||
|
||||
.. important::
|
||||
@ -70,7 +70,7 @@ Customers using SDD as payment method get prompted to add their IBAN, email addr
|
||||
their SEPA Direct Debit mandate.
|
||||
|
||||
.. todo::
|
||||
Add link to future **Payment Acquirer** documentation.
|
||||
Add link to future **Payment Provider** documentation.
|
||||
|
||||
Close or revoke a mandate
|
||||
-------------------------
|
||||
|
@ -7,18 +7,18 @@ To make it more convenient for your customers to pay the invoices you issue, you
|
||||
allows your customers to see their invoices online and pay directly with their favorite payment
|
||||
method, making the payment process much easier.
|
||||
|
||||
.. image:: online_payment/online-payment-acquirers.png
|
||||
.. image:: online_payment/online-payment-providers.png
|
||||
:align: center
|
||||
:alt: Payment acquirer choice after having clicked on "Pay Now"
|
||||
:alt: Payment provider choice after having clicked on "Pay Now"
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
Make sure your :ref:`Payment Acquirers are correctly configured <payment_acquirers/configuration>`.
|
||||
Make sure your :ref:`Payment Providers are correctly configured <payment_providers/configuration>`.
|
||||
|
||||
.. note::
|
||||
By default, ":doc:`Wire Transfer </applications/finance/payment_acquirers/wire_transfer>`" is the only
|
||||
Payment Acquirer activated, but you still have to fill out the payment details.
|
||||
By default, ":doc:`Wire Transfer </applications/finance/payment_providers/wire_transfer>`" is the only
|
||||
Payment Provider activated, but you still have to fill out the payment details.
|
||||
|
||||
To activate the Invoice Online Payment, go to :menuselection:`Accounting --> Configuration -->
|
||||
Settings --> Customer Payments`, enable **Invoice Online Payment**, and click on *Save*.
|
||||
@ -34,7 +34,7 @@ Portal**.
|
||||
:align: center
|
||||
:alt: Email with a link to view the invoice online on the Customer Portal.
|
||||
|
||||
They can choose which Payment Acquirer to use by clicking on *Pay Now*.
|
||||
They can choose which Payment Provider to use by clicking on *Pay Now*.
|
||||
|
||||
.. image:: online_payment/online-payment-pay-now.png
|
||||
:align: center
|
||||
@ -42,4 +42,4 @@ They can choose which Payment Acquirer to use by clicking on *Pay Now*.
|
||||
|
||||
.. seealso::
|
||||
|
||||
- :doc:`/applications/finance/payment_acquirers`
|
||||
- :doc:`/applications/finance/payment_providers`
|
||||
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
@ -1,29 +1,29 @@
|
||||
:show-content:
|
||||
|
||||
=================================================
|
||||
Payment acquirers (credit cards, online payments)
|
||||
Payment providers (credit cards, online payments)
|
||||
=================================================
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
payment_acquirers/wire_transfer
|
||||
payment_acquirers/adyen
|
||||
payment_acquirers/alipay
|
||||
payment_acquirers/amazon_payment_services
|
||||
payment_acquirers/asiapay
|
||||
payment_acquirers/authorize
|
||||
payment_acquirers/buckaroo
|
||||
payment_acquirers/flutterwave
|
||||
payment_acquirers/mercado_pago
|
||||
payment_acquirers/mollie
|
||||
payment_acquirers/ogone
|
||||
payment_acquirers/paypal
|
||||
payment_acquirers/razorpay
|
||||
payment_acquirers/sips
|
||||
payment_acquirers/stripe
|
||||
payment_providers/wire_transfer
|
||||
payment_providers/adyen
|
||||
payment_providers/alipay
|
||||
payment_providers/amazon_payment_services
|
||||
payment_providers/asiapay
|
||||
payment_providers/authorize
|
||||
payment_providers/buckaroo
|
||||
payment_providers/flutterwave
|
||||
payment_providers/mercado_pago
|
||||
payment_providers/mollie
|
||||
payment_providers/ogone
|
||||
payment_providers/paypal
|
||||
payment_providers/razorpay
|
||||
payment_providers/sips
|
||||
payment_providers/stripe
|
||||
|
||||
Odoo embeds several **payment acquirers** that allow your customers to pay on their *Customer
|
||||
Odoo embeds several **payment providers** that allow your customers to pay on their *Customer
|
||||
Portals* or your *eCommerce website*. They can pay sales orders, invoices, or subscriptions with
|
||||
recurring payments with their favorite payment methods such as **Credit Cards**.
|
||||
|
||||
@ -31,30 +31,30 @@ Offering several payment methods increases the chances of getting paid in time,
|
||||
as you make it more convenient for your customers to pay with the payment method they prefer and
|
||||
trust.
|
||||
|
||||
.. image:: payment_acquirers/online-payment.png
|
||||
.. image:: payment_providers/online-payment.png
|
||||
:align: center
|
||||
:alt: Pay online in the customer portal and select which payment acquirer to use.
|
||||
:alt: Pay online in the customer portal and select which payment provider to use.
|
||||
|
||||
.. note::
|
||||
Odoo apps delegate the handling of sensitive information to the certified payment acquirer so
|
||||
Odoo apps delegate the handling of sensitive information to the certified payment provider so
|
||||
that you don't ever have to worry about PCI compliance.
|
||||
|
||||
This means that no sensitive information (such as credit card numbers) is stored on Odoo servers
|
||||
or Odoo databases hosted elsewhere. Instead, Odoo apps use a unique reference number to the data
|
||||
stored safely in the payment acquirers' systems.
|
||||
stored safely in the payment providers' systems.
|
||||
|
||||
.. _payment_acquirers/supported_acquirers:
|
||||
.. _payment_providers/supported_providers:
|
||||
|
||||
Supported payment acquirers
|
||||
Supported payment providers
|
||||
===========================
|
||||
|
||||
From an accounting perspective, we can distinguish two types of payment acquirers: the payment
|
||||
acquirers that are third-party services and require you to follow another accounting workflow, and
|
||||
From an accounting perspective, we can distinguish two types of payment providers: the payment
|
||||
providers that are third-party services and require you to follow another accounting workflow, and
|
||||
the payments that go directly on the bank account and follow the usual reconciliation workflow.
|
||||
|
||||
.. _payment_acquirers/online_acquirers:
|
||||
.. _payment_providers/online_providers:
|
||||
|
||||
Online payment acquirers
|
||||
Online payment providers
|
||||
------------------------
|
||||
|
||||
.. list-table::
|
||||
@ -64,78 +64,78 @@ Online payment acquirers
|
||||
|
||||
* -
|
||||
- Payment flow
|
||||
- :ref:`Tokenization <payment_acquirers/features/tokenization>`
|
||||
- :ref:`Manual capture <payment_acquirers/features/manual_capture>`
|
||||
- :ref:`Refunds <payment_acquirers/features/refund>`
|
||||
- :ref:`Express checkout <payment_acquirers/features/express_checkout>`
|
||||
* - :doc:`Adyen <payment_acquirers/adyen>`
|
||||
- :ref:`Tokenization <payment_providers/features/tokenization>`
|
||||
- :ref:`Manual capture <payment_providers/features/manual_capture>`
|
||||
- :ref:`Refunds <payment_providers/features/refund>`
|
||||
- :ref:`Express checkout <payment_providers/features/express_checkout>`
|
||||
* - :doc:`Adyen <payment_providers/adyen>`
|
||||
- Payment from Odoo
|
||||
- |V|
|
||||
- Full only
|
||||
- Full and partial
|
||||
-
|
||||
* - :doc:`Amazon Payment Services <payment_acquirers/amazon_payment_services>`
|
||||
- Payment from the acquirer website
|
||||
* - :doc:`Amazon Payment Services <payment_providers/amazon_payment_services>`
|
||||
- Payment from the provider website
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`AsiaPay <payment_acquirers/asiapay>`
|
||||
- Payment from the acquirer website
|
||||
* - :doc:`AsiaPay <payment_providers/asiapay>`
|
||||
- Payment from the provider website
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Authorize.Net <payment_acquirers/authorize>`
|
||||
* - :doc:`Authorize.Net <payment_providers/authorize>`
|
||||
- Payment from Odoo
|
||||
- |V|
|
||||
- Full only
|
||||
- Full only
|
||||
-
|
||||
* - :doc:`Buckaroo <payment_acquirers/buckaroo>`
|
||||
- Payment from the acquirer website
|
||||
* - :doc:`Buckaroo <payment_providers/buckaroo>`
|
||||
- Payment from the provider website
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Flutterwave <payment_acquirers/flutterwave>`
|
||||
- Payment from the acquirer website
|
||||
* - :doc:`Flutterwave <payment_providers/flutterwave>`
|
||||
- Payment from the provider website
|
||||
- |V|
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Mercado Pago <payment_acquirers/mercado_pago>`
|
||||
- Payment from the acquirer website
|
||||
* - :doc:`Mercado Pago <payment_providers/mercado_pago>`
|
||||
- Payment from the provider website
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Mollie <payment_acquirers/mollie>`
|
||||
- Payment from the acquirer website
|
||||
* - :doc:`Mollie <payment_providers/mollie>`
|
||||
- Payment from the provider website
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`PayPal <payment_acquirers/paypal>`
|
||||
- Payment from the acquirer website
|
||||
* - :doc:`PayPal <payment_providers/paypal>`
|
||||
- Payment from the provider website
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Razorpay <payment_acquirers/razorpay>`
|
||||
* - :doc:`Razorpay <payment_providers/razorpay>`
|
||||
- Payment from Odoo
|
||||
-
|
||||
- Full only
|
||||
- Full and partial
|
||||
-
|
||||
* - :doc:`SIPS <payment_acquirers/sips>`
|
||||
- Payment from the acquirer website
|
||||
* - :doc:`SIPS <payment_providers/sips>`
|
||||
- Payment from the provider website
|
||||
-
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Stripe <payment_acquirers/stripe>`
|
||||
- Payment from the acquirer website
|
||||
* - :doc:`Stripe <payment_providers/stripe>`
|
||||
- Payment from the provider website
|
||||
- |V|
|
||||
- Full only
|
||||
- Full and partial
|
||||
@ -146,16 +146,16 @@ Online payment acquirers
|
||||
.. note::
|
||||
Some of these online payment providers can also be added as :doc:`bank accounts
|
||||
<../finance/accounting/bank/setup/bank_accounts>`, but this is **not** the same process as adding
|
||||
them as payment acquirers. Payment acquirers allow customers to pay online, and bank accounts are
|
||||
them as payment providers. Payment providers allow customers to pay online, and bank accounts are
|
||||
added and configured on your Accounting app to do a bank reconciliation, which is an accounting
|
||||
control process.
|
||||
|
||||
.. _payment_acquirers/bank_payments:
|
||||
.. _payment_providers/bank_payments:
|
||||
|
||||
Bank payments
|
||||
-------------
|
||||
|
||||
- | :doc:`Wire Transfer <payment_acquirers/wire_transfer>`
|
||||
- | :doc:`Wire Transfer <payment_providers/wire_transfer>`
|
||||
| When selected, Odoo displays your payment information with a payment reference. You have to
|
||||
approve the payment manually once you have received it on your bank account.
|
||||
- | SEPA Direct Debit
|
||||
@ -163,39 +163,39 @@ Bank payments
|
||||
directly. :doc:`Click here <../finance/accounting/receivables/customer_payments/batch_sdd>` for
|
||||
more information about this payment method.
|
||||
|
||||
.. _payment_acquirers/features:
|
||||
.. _payment_providers/features:
|
||||
|
||||
Additional features
|
||||
===================
|
||||
|
||||
Some payment acquirers support additional features for the payment flow. Refer to the :ref:`table
|
||||
above <payment_acquirers/online_acquirers>` to check if your payment acquirer supports these
|
||||
Some payment providers support additional features for the payment flow. Refer to the :ref:`table
|
||||
above <payment_providers/online_providers>` to check if your payment provider supports these
|
||||
features.
|
||||
|
||||
.. _payment_acquirers/features/tokenization:
|
||||
.. _payment_providers/features/tokenization:
|
||||
|
||||
Tokenization
|
||||
------------
|
||||
|
||||
If your payment acquirer supports this feature, customers can choose to save their card for later. A
|
||||
If your payment provider supports this feature, customers can choose to save their card for later. A
|
||||
**payment token** is created in Odoo and can be used as a payment method for subsequent payments
|
||||
without having to enter the card details again. This is particularly useful for the eCommerce
|
||||
conversion rate and for subscriptions that use recurring payments.
|
||||
|
||||
Enable this feature by navigating to the :guilabel:`Configuration` tab from your payment acquirer
|
||||
Enable this feature by navigating to the :guilabel:`Configuration` tab from your payment provider
|
||||
and by ticking the :guilabel:`Allow Saving Payment Methods` checkbox.
|
||||
|
||||
.. note::
|
||||
You remain fully PCI-compliant when you enable this feature because Odoo does not store the card
|
||||
details directly. Instead, it creates a payment token that only holds a reference to the card
|
||||
details stored on the payment acquirer's server.
|
||||
details stored on the payment provider's server.
|
||||
|
||||
.. _payment_acquirers/features/manual_capture:
|
||||
.. _payment_providers/features/manual_capture:
|
||||
|
||||
Manual capture
|
||||
--------------
|
||||
|
||||
If your payment acquirer supports this feature, you can authorize and capture payments in two steps
|
||||
If your payment provider supports this feature, you can authorize and capture payments in two steps
|
||||
instead of one. When you authorize a payment, the funds are reserved on the customer's payment
|
||||
method but they are not immediately charged. The charge is only made when you manually capture the
|
||||
payment later on. You can also void the authorization to release the reserved funds; this is
|
||||
@ -205,11 +205,11 @@ situations:
|
||||
- Receive the payment confirmation and wait until the order is shipped to capture the payment.
|
||||
- Review and verify that orders are legitimate before the payment is completed and the fulfillment
|
||||
process starts.
|
||||
- Avoid potentially high processing fees for cancelled payments: payment acquirers will not charge
|
||||
- Avoid potentially high processing fees for cancelled payments: payment providers will not charge
|
||||
you for voiding an authorization.
|
||||
- Hold a security deposit to return later, minus any deductions (e.g., after a damage).
|
||||
|
||||
Enable this feature by navigating to the :guilabel:`Configuration` tab from your payment acquirer
|
||||
Enable this feature by navigating to the :guilabel:`Configuration` tab from your payment provider
|
||||
and by ticking the :guilabel:`Capture Amount Manually` checkbox.
|
||||
|
||||
To capture the payment after it was authorized, go to the related sales order or invoice and click
|
||||
@ -217,114 +217,114 @@ on the :guilabel:`CAPTURE TRANSACTION` button. To release the funds, click on th
|
||||
TRANSACTION` button.
|
||||
|
||||
.. note::
|
||||
- Some payment acquirers support capturing only part of the authorized amount. The remaining
|
||||
amount can then be either captured or voided. These acquirers have the value **Full and
|
||||
partial** in the :ref:`table above <payment_acquirers/online_acquirers>`. The acquirers that
|
||||
- Some payment providers support capturing only part of the authorized amount. The remaining
|
||||
amount can then be either captured or voided. These providers have the value **Full and
|
||||
partial** in the :ref:`table above <payment_providers/online_providers>`. The providers that
|
||||
only support capturing or voiding the full amount have the value **Full only**.
|
||||
- The funds are likely not reserved forever. After a certain time, they may be automatically
|
||||
released back to the customer's payment method. Refer to your payment acquirer's documentation
|
||||
released back to the customer's payment method. Refer to your payment provider's documentation
|
||||
for the exact reservation duration.
|
||||
- Odoo does not support this feature for all payment acquirers but some allow the manual capture
|
||||
- Odoo does not support this feature for all payment providers but some allow the manual capture
|
||||
from their website interface.
|
||||
|
||||
.. _payment_acquirers/features/refund:
|
||||
.. _payment_providers/features/refund:
|
||||
|
||||
Refunds
|
||||
-------
|
||||
|
||||
If your payment acquirer supports this feature, you can refund payments directly from Odoo. It does
|
||||
If your payment provider supports this feature, you can refund payments directly from Odoo. It does
|
||||
not need to be enabled first. To refund a customer payment, navigate to it and click on the
|
||||
:guilabel:`REFUND` button.
|
||||
|
||||
.. note::
|
||||
- Some payment acquirers support refunding only part of the amount. The remaining amount can then
|
||||
optionally be refunded too. These acquirers have the value **Full and partial** in the
|
||||
:ref:`table above <payment_acquirers/online_acquirers>`. The acquirers that only support
|
||||
- Some payment providers support refunding only part of the amount. The remaining amount can then
|
||||
optionally be refunded too. These providers have the value **Full and partial** in the
|
||||
:ref:`table above <payment_providers/online_providers>`. The providers that only support
|
||||
refunding the full amount have the value **Full only**.
|
||||
- Odoo does not support this feature for all payment acquirers but some allow to refund payments
|
||||
- Odoo does not support this feature for all payment providers but some allow to refund payments
|
||||
from their website interface.
|
||||
|
||||
.. _payment_acquirers/features/express_checkout:
|
||||
.. _payment_providers/features/express_checkout:
|
||||
|
||||
Express checkout
|
||||
----------------
|
||||
|
||||
If your payment acquirer supports this feature, customers can use the **Google Pay** and **Apple
|
||||
If your payment provider supports this feature, customers can use the **Google Pay** and **Apple
|
||||
Pay** buttons to pay their eCommerce orders in one click without filling the contact form. Using one
|
||||
of those buttons, they'll go straight from the cart to the confirmation page, stopping by the
|
||||
payment form of Google or Apple to validate the payment.
|
||||
|
||||
Enable this feature by navigating to the :guilabel:`Configuration` tab from your payment acquirer
|
||||
Enable this feature by navigating to the :guilabel:`Configuration` tab from your payment provider
|
||||
and by ticking the :guilabel:`Allow Express Checkout` checkbox.
|
||||
|
||||
.. note::
|
||||
All prices shown in the express checkout payment form are always taxes included.
|
||||
|
||||
.. _payment_acquirers/configuration:
|
||||
.. _payment_providers/configuration:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
.. note::
|
||||
Each acquirer has its specific configuration flow, depending on :ref:`which feature is available
|
||||
<payment_acquirers/online_acquirers>`.
|
||||
Each provider has its specific configuration flow, depending on :ref:`which feature is available
|
||||
<payment_providers/online_providers>`.
|
||||
|
||||
.. _payment_acquirers/add_new:
|
||||
.. _payment_providers/add_new:
|
||||
|
||||
Add a new payment acquirer
|
||||
Add a new payment provider
|
||||
--------------------------
|
||||
|
||||
To add a new payment acquirer and make it available to your customers, go to
|
||||
:menuselection:`Accounting --> Configuration --> Payment Acquirers`, look for your payment acquirer,
|
||||
install the related module, and activate it. To do so, open the payment acquirer and change its
|
||||
To add a new payment provider and make it available to your customers, go to
|
||||
:menuselection:`Accounting --> Configuration --> Payment Providers`, look for your payment provider,
|
||||
install the related module, and activate it. To do so, open the payment provider and change its
|
||||
state from *Disabled* to *Enabled*.
|
||||
|
||||
.. image:: payment_acquirers/activation.png
|
||||
.. image:: payment_providers/activation.png
|
||||
:align: center
|
||||
:alt: Click on install, then on activate to make the payment acquirer available on Odoo.
|
||||
:alt: Click on install, then on activate to make the payment provider available on Odoo.
|
||||
|
||||
.. warning::
|
||||
We recommend using the *Test Mode* on a duplicated database or a test database. The Test Mode is
|
||||
meant to be used with your test/sandbox credentials, but Odoo generates Sales Orders and Invoices
|
||||
as usual. It isn't always possible to cancel an invoice, and this could create some issues with
|
||||
your invoices numbering if you were to test your payment acquirers on your main database.
|
||||
your invoices numbering if you were to test your payment providers on your main database.
|
||||
|
||||
.. _payment_acquirers/credentials_tab:
|
||||
.. _payment_providers/credentials_tab:
|
||||
|
||||
Credentials tab
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
If not done yet, go to the online payment provider website, create an account, and make sure to have
|
||||
the credentials required for third-party use. Odoo requires these credentials to communicate with
|
||||
the payment acquirer.
|
||||
the payment provider.
|
||||
|
||||
The form in this section is specific to the payment acquirer you are configuring. Please refer to
|
||||
The form in this section is specific to the payment provider you are configuring. Please refer to
|
||||
the related documentation for more information.
|
||||
|
||||
.. _payment_acquirers/configuration_tab:
|
||||
.. _payment_providers/configuration_tab:
|
||||
|
||||
Configuration tab
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
You can change the payment acquirer's front-end appearance by modifying its name under the
|
||||
You can change the payment provider's front-end appearance by modifying its name under the
|
||||
**Displayed as** field and which credit card icons to display under the **Supported Payment Icons**
|
||||
field.
|
||||
|
||||
.. _payment_acquirers/countries:
|
||||
.. _payment_providers/countries:
|
||||
|
||||
Countries
|
||||
*********
|
||||
|
||||
Restrict the use of the payment acquirer to a selection of countries. Leave this field blank to make
|
||||
the payment acquirer available in all countries.
|
||||
Restrict the use of the payment provider to a selection of countries. Leave this field blank to make
|
||||
the payment provider available in all countries.
|
||||
|
||||
.. _payment_acquirers/journal:
|
||||
.. _payment_providers/journal:
|
||||
|
||||
Maximum Amount
|
||||
**************
|
||||
|
||||
Restrict the maximum amount that can be paid with the selected acquirer. Leave this field to `0.00`
|
||||
to make the payment acquirer available regardless of the payment amount.
|
||||
Restrict the maximum amount that can be paid with the selected provider. Leave this field to `0.00`
|
||||
to make the payment provider available regardless of the payment amount.
|
||||
|
||||
.. important::
|
||||
This feature is not intended to work on pages which allow the customer to update the payment
|
||||
@ -334,28 +334,28 @@ to make the payment acquirer available regardless of the payment amount.
|
||||
Payment journal
|
||||
***************
|
||||
|
||||
The **Payment journal** selected for your payment acquirer must be a *Bank* journal.
|
||||
The **Payment journal** selected for your payment provider must be a *Bank* journal.
|
||||
|
||||
.. _payment_acquirers/publish:
|
||||
.. _payment_providers/publish:
|
||||
|
||||
Publish on the website
|
||||
----------------------
|
||||
|
||||
By default, payment acquirers are *unpublished*, which means that only internal users can see them
|
||||
on the website. Your customers cannot make payments through an unpublished acquirer but they can
|
||||
By default, payment providers are *unpublished*, which means that only internal users can see them
|
||||
on the website. Your customers cannot make payments through an unpublished provider but they can
|
||||
still manage :dfn:`(delete and assign to a subscription)` their already existing tokens linked to
|
||||
such an acquirer. This conveniently allows you to test an acquirer while preventing making payments
|
||||
such an provider. This conveniently allows you to test an provider while preventing making payments
|
||||
and registering new tokens.
|
||||
|
||||
Click on the :guilabel:`Publish` button located in the top right corner of the acquirer's form to
|
||||
Click on the :guilabel:`Publish` button located in the top right corner of the provider's form to
|
||||
publish it on the website and make it available to your customers. Click on the
|
||||
:guilabel:`Unpublish` button to unpublish it.
|
||||
|
||||
.. tip::
|
||||
Payment acquirers are automatically published and unpublished when you respectively change their
|
||||
Payment providers are automatically published and unpublished when you respectively change their
|
||||
state to `enabled` and `test`.
|
||||
|
||||
.. _payment_acquirers/accounting:
|
||||
.. _payment_providers/accounting:
|
||||
|
||||
Accounting perspective
|
||||
======================
|
||||
@ -365,7 +365,7 @@ reconciliation workflows. However, payments recorded with **Online Payment Provi
|
||||
to consider how you want to record your payments' journal entries. We recommend you to ask your
|
||||
accountant for advice.
|
||||
|
||||
You need to select a *Payment Journal* on your acquirer configuration to record the payments,
|
||||
You need to select a *Payment Journal* on your provider configuration to record the payments,
|
||||
on a **Outstanding Account**. The Journal's **type** must be *Bank Journal*.
|
||||
|
||||
You can use a single journal for many payment methods. And for each payment method, you can either:
|
||||
@ -373,7 +373,7 @@ You can use a single journal for many payment methods. And for each payment meth
|
||||
- Define an **Accounting Account** to separate these payments from another payment method.
|
||||
- Leave blank to fallback on the default account, which you can see or change in the settings.
|
||||
|
||||
.. image:: payment_acquirers/bank_journal.png
|
||||
.. image:: payment_providers/bank_journal.png
|
||||
:align: center
|
||||
:alt: A bank journal in the "Incoming Payments Tab".
|
||||
|
||||
@ -381,17 +381,17 @@ You can have the same bank account for the whole company, or for some journals o
|
||||
payment method... What best suit your needs.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`payment_acquirers/wire_transfer`
|
||||
- :doc:`payment_acquirers/adyen`
|
||||
- :doc:`payment_acquirers/alipay`
|
||||
- :doc:`payment_acquirers/authorize`
|
||||
- :doc:`payment_acquirers/asiapay`
|
||||
- :doc:`payment_acquirers/buckaroo`
|
||||
- :doc:`payment_acquirers/mercado_pago`
|
||||
- :doc:`payment_acquirers/mollie`
|
||||
- :doc:`payment_acquirers/ogone`
|
||||
- :doc:`payment_acquirers/paypal`
|
||||
- :doc:`payment_acquirers/razorpay`
|
||||
- :doc:`payment_acquirers/sips`
|
||||
- :doc:`payment_acquirers/stripe`
|
||||
- :doc:`../websites/ecommerce/shopper_experience/payment_acquirer`
|
||||
- :doc:`payment_providers/wire_transfer`
|
||||
- :doc:`payment_providers/adyen`
|
||||
- :doc:`payment_providers/alipay`
|
||||
- :doc:`payment_providers/authorize`
|
||||
- :doc:`payment_providers/asiapay`
|
||||
- :doc:`payment_providers/buckaroo`
|
||||
- :doc:`payment_providers/mercado_pago`
|
||||
- :doc:`payment_providers/mollie`
|
||||
- :doc:`payment_providers/ogone`
|
||||
- :doc:`payment_providers/paypal`
|
||||
- :doc:`payment_providers/razorpay`
|
||||
- :doc:`payment_providers/sips`
|
||||
- :doc:`payment_providers/stripe`
|
||||
- :doc:`../websites/ecommerce/shopper_experience/payment_providers`
|
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 24 KiB |
@ -9,7 +9,7 @@ Configuration
|
||||
=============
|
||||
|
||||
.. seealso::
|
||||
:ref:`payment_acquirers/add_new`
|
||||
:ref:`payment_providers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
@ -28,7 +28,7 @@ the **Credentials** tab.
|
||||
|
||||
.. important::
|
||||
If you are trying Adyen as a test, with an Adyen *test account*, head to
|
||||
:menuselection:`Accounting --> Configuration --> Payment Acquirers`. There, click on
|
||||
:menuselection:`Accounting --> Configuration --> Payment Providers`. There, click on
|
||||
:guilabel:`Adyen`, enable :guilabel:`Test Mode` and enter your credentials in the
|
||||
:guilabel:`Credentials` tab.
|
||||
|
||||
@ -114,7 +114,7 @@ Place a hold on a card
|
||||
Adyen allows you to capture an amount manually instead of having an immediate capture.
|
||||
|
||||
To set it up, enable the **Capture Amount Manually** option on Odoo, as explained in the
|
||||
:ref:`payment acquirers documentation <payment_acquirers/features/manual_capture>`.
|
||||
:ref:`payment providers documentation <payment_providers/features/manual_capture>`.
|
||||
|
||||
Then, open your Adyen Merchant Account, go to :menuselection:`Account --> Settings`, and set the
|
||||
**Capture Delay** to **manual**.
|
||||
@ -135,4 +135,4 @@ Then, open your Adyen Merchant Account, go to :menuselection:`Account --> Settin
|
||||
**revoke** it.
|
||||
|
||||
.. seealso::
|
||||
:doc:`../payment_acquirers`
|
||||
:doc:`../payment_providers`
|
Before Width: | Height: | Size: 7.7 KiB After Width: | Height: | Size: 7.7 KiB |
Before Width: | Height: | Size: 7.0 KiB After Width: | Height: | Size: 7.0 KiB |
Before Width: | Height: | Size: 29 KiB After Width: | Height: | Size: 29 KiB |
Before Width: | Height: | Size: 8.2 KiB After Width: | Height: | Size: 8.2 KiB |
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 12 KiB |
Before Width: | Height: | Size: 7.6 KiB After Width: | Height: | Size: 7.6 KiB |
@ -12,7 +12,7 @@ Configuration
|
||||
=============
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
- :ref:`payment_providers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
@ -36,4 +36,4 @@ To retrieve them, log into your Alipay account, they are on the front page.
|
||||
recommend doing this on a test Odoo database, rather than on your main database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
@ -5,7 +5,7 @@ Amazon Payment Services
|
||||
`Amazon Payment Services <https://paymentservices.amazon.com/>`_ or APS is an online payment provider
|
||||
established in Dubai offering several online payment options.
|
||||
|
||||
.. _payment_acquirers/aps/configure-dashboard:
|
||||
.. _payment_providers/aps/configure-dashboard:
|
||||
|
||||
Configuration on APS Dashboard
|
||||
==============================
|
||||
@ -31,14 +31,14 @@ Configuration on APS Dashboard
|
||||
look and feel of the Amazon Payment Services payment page (where customers fill out their
|
||||
credit card details during payment).
|
||||
|
||||
.. _payment_acquirers/aps/configure-odoo:
|
||||
.. _payment_providers/aps/configure-odoo:
|
||||
|
||||
Configuration on Odoo
|
||||
=====================
|
||||
|
||||
#. :ref:`Navigate to the payment acquirer Amazon Payment Services <payment_acquirers/add_new>`,
|
||||
#. :ref:`Navigate to the payment provider Amazon Payment Services <payment_providers/add_new>`,
|
||||
change its state to :guilabel:`Enabled`, and make sure it is :guilabel:`Published`.
|
||||
#. In the :guilabel:`Credentials` tab, fill the :guilabel:`Merchant Identifier`,
|
||||
:guilabel:`Access Code`, :guilabel:`SHA Request Phrase` and :guilabel:`SHA Response Phrase` with
|
||||
the values you saved at the step :ref:`payment_acquirers/aps/configure-dashboard`.
|
||||
the values you saved at the step :ref:`payment_providers/aps/configure-dashboard`.
|
||||
#. Configure the rest of the options to your liking.
|
@ -5,7 +5,7 @@ AsiaPay
|
||||
`AsiaPay <https://www.asiapay.com/>`_ is an online payments provider established in Hong Kong and
|
||||
covering several Asian countries and payment methods.
|
||||
|
||||
.. _payment_acquirers/asiapay/configure_dashboard:
|
||||
.. _payment_providers/asiapay/configure_dashboard:
|
||||
|
||||
Configuration on AsiaPay Dashboard
|
||||
==================================
|
||||
@ -21,21 +21,21 @@ Configuration on AsiaPay Dashboard
|
||||
| Click on :guilabel:`Test` to check if the webhook is working correctly.
|
||||
#. Click on :guilabel:`Update` to finalize the configuration.
|
||||
|
||||
.. _payment_acquirers/asiapay/configure_odoo:
|
||||
.. _payment_providers/asiapay/configure_odoo:
|
||||
|
||||
Configuration on Odoo
|
||||
=====================
|
||||
|
||||
#. :ref:`Navigate to the payment acquirer AsiaPay <payment_acquirers/add_new>` and change its state
|
||||
#. :ref:`Navigate to the payment provider AsiaPay <payment_providers/add_new>` and change its state
|
||||
to :guilabel:`Enabled`.
|
||||
#. | In the :guilabel:`Credentials` tab, fill the :guilabel:`Merchant ID`, :guilabel:`Currency`, and
|
||||
:guilabel:`Secure Hash Secret` with the values you saved at the step
|
||||
:ref:`payment_acquirers/asiapay/configure_dashboard`.
|
||||
| By default, the payment acquirer AsiaPay is configured to verify the secret hash with the hash
|
||||
:ref:`payment_providers/asiapay/configure_dashboard`.
|
||||
| By default, the payment provider AsiaPay is configured to verify the secret hash with the hash
|
||||
function `SHA1`. If a different function is :ref:`set on your account
|
||||
<payment_acquirers/asiapay/configure_dashboard>`, activate the :ref:`developer mode
|
||||
<payment_providers/asiapay/configure_dashboard>`, activate the :ref:`developer mode
|
||||
<developer-mode>` and set the same value to the field :guilabel:`Secure Hash Function` in Odoo.
|
||||
#. Configure the rest of the options to your liking.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
@ -9,7 +9,7 @@ Configuration
|
||||
=============
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
- :ref:`payment_providers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
@ -43,11 +43,11 @@ Place a hold on a card
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
With Authorize.net, you can enable the :ref:`manual capture
|
||||
<payment_acquirers/features/manual_capture>`. If enabled, the funds are reserved for 30 days on the
|
||||
<payment_providers/features/manual_capture>`. If enabled, the funds are reserved for 30 days on the
|
||||
customer's card, but not charged yet.
|
||||
|
||||
.. warning::
|
||||
After **30 days**, the transaction is **voided automatically** by Authorize.net.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 21 KiB |
@ -25,7 +25,7 @@ Configuration on Odoo
|
||||
=====================
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
- :ref:`payment_providers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
@ -60,4 +60,4 @@ In order to retrieve the Website Key, log into Buckaroo Plaza, go to
|
||||
recommend doing this on a test Odoo database, rather than on your main database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
@ -5,7 +5,7 @@ Flutterwave
|
||||
`Flutterwave <https://flutterwave.com/>`_ is an online payments provider established in Nigeria and
|
||||
covering several African countries and payment methods.
|
||||
|
||||
.. _payment_acquirers/flutterwave/configure_dashboard:
|
||||
.. _payment_providers/flutterwave/configure_dashboard:
|
||||
|
||||
Configuration on Flutterwave Dashboard
|
||||
======================================
|
||||
@ -20,16 +20,16 @@ Configuration on Flutterwave Dashboard
|
||||
#. Make sure all the remaining checkboxes are ticked.
|
||||
#. Click on **Save** to finalize the configuration.
|
||||
|
||||
.. _payment_acquirers/flutterwave/configure_odoo:
|
||||
.. _payment_providers/flutterwave/configure_odoo:
|
||||
|
||||
Configuration on Odoo
|
||||
=====================
|
||||
|
||||
#. :ref:`Navigate to the payment acquirer Flutterwave <payment_acquirers/add_new>` and change its
|
||||
#. :ref:`Navigate to the payment provider Flutterwave <payment_providers/add_new>` and change its
|
||||
state to :guilabel:`Enabled`.
|
||||
#. In the :guilabel:`Credentials` tab, fill the :guilabel:`Public Key`, :guilabel:`Secret Key`, and
|
||||
:guilabel:`Webhook Secret` with the values you saved at the step
|
||||
:ref:`payment_acquirers/flutterwave/configure_dashboard`.
|
||||
:ref:`payment_providers/flutterwave/configure_dashboard`.
|
||||
#. Configure the rest of the options to your liking.
|
||||
|
||||
.. important::
|
||||
@ -38,4 +38,4 @@ Configuration on Odoo
|
||||
Flutterwave Dashboard and then to :menuselection:`Settings --> Account Settings`.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
@ -5,7 +5,7 @@ Mercado Pago
|
||||
`Mercado Pago <https://www.mercadopago.com/>`_ is an online payment provider covering several
|
||||
countries, currencies and payment methods in Latin America.
|
||||
|
||||
.. _payment_acquirers/mercado_pago/configure_dashboard:
|
||||
.. _payment_providers/mercado_pago/configure_dashboard:
|
||||
|
||||
Configuration on Mercado Pago Dashboard
|
||||
=======================================
|
||||
@ -15,16 +15,16 @@ Configuration on Mercado Pago Dashboard
|
||||
#. Go to :menuselection:`Production Credentials` or :menuselection:`Credentials` if your are in
|
||||
a *Test* environment and copy your **Access Token**
|
||||
|
||||
.. _payment_acquirers/mercado_pago/configure_odoo:
|
||||
.. _payment_providers/mercado_pago/configure_odoo:
|
||||
|
||||
Configuration on Odoo
|
||||
=====================
|
||||
|
||||
#. :ref:`Navigate to the payment acquirer Mercado Pago <payment_acquirers/add_new>` and change its
|
||||
#. :ref:`Navigate to the payment provider Mercado Pago <payment_providers/add_new>` and change its
|
||||
state to :guilabel:`Enabled`.
|
||||
#. In the :guilabel:`Credentials` tab, fill the :guilabel:`Access Token` with the value
|
||||
you saved at the step :ref:`payment_acquirers/mercado_pago/configure_dashboard`.
|
||||
you saved at the step :ref:`payment_providers/mercado_pago/configure_dashboard`.
|
||||
#. Configure the rest of the options to your liking.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
@ -8,14 +8,14 @@ Configuration
|
||||
=============
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
- :ref:`payment_providers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
|
||||
Odoo needs your **API Credentials** to connect with your Mollie account, which comprise:
|
||||
|
||||
- **API Key**: The test or live API Key depending on the configuration of the acquirer.
|
||||
- **API Key**: The test or live API Key depending on the configuration of the provider.
|
||||
|
||||
You can copy your credentials from your Mollie account, and paste them in the related fields under
|
||||
the **Credentials** tab.
|
||||
@ -28,4 +28,4 @@ To retrieve your API key, log into your Mollie account, go to
|
||||
We recommend doing this on a test Odoo database, rather than on your main database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
@ -6,7 +6,7 @@ Ogone
|
||||
company that provides the technology involved in secure electronic transactions.
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
- :ref:`payment_providers/add_new`
|
||||
- `Ogone's documentation <https://epayments-support.ingenico.com/get-started/>`_.
|
||||
|
||||
.. warning::
|
||||
@ -53,8 +53,8 @@ Technical Information --> Global Security Parameters`, select :guilabel:`SHA-512
|
||||
|
||||
.. tip::
|
||||
If you need to use another algorithm, such as `sha-1` or `sha-256`, within Odoo, activate the
|
||||
:ref:`developer mode <developer-mode>` and go to the **Payment Acquirers** page in
|
||||
:menuselection:`Accounting --> Configuration --> Payment Acquirers`. Click on :guilabel:`Ogone`,
|
||||
:ref:`developer mode <developer-mode>` and go to the **Payment Providers** page in
|
||||
:menuselection:`Accounting --> Configuration --> Payment Providers`. Click on :guilabel:`Ogone`,
|
||||
and in the :guilabel:`Credentials` tab, select the algorithm you wish to use in the
|
||||
:guilabel:`Hash function` field.
|
||||
|
||||
@ -102,6 +102,6 @@ to save the card information should be displayed, etc.
|
||||
Settings in Odoo
|
||||
================
|
||||
|
||||
To set up Ogone in Odoo, head to :menuselection:`Accounting --> Configuration --> Payment Acquirers`
|
||||
and open the Ogone acquirer. In the :guilabel:`Credentials` tab, enter the **PSPID** of your Ogone
|
||||
To set up Ogone in Odoo, head to :menuselection:`Accounting --> Configuration --> Payment Providers`
|
||||
and open the Ogone provider. In the :guilabel:`Credentials` tab, enter the **PSPID** of your Ogone
|
||||
account, and fill out the other fields as configured in your :ref:`Ogone portal <ogone/ogone>`.
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
@ -11,7 +11,7 @@ Settings in Odoo
|
||||
================
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
- :ref:`payment_providers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
@ -141,4 +141,4 @@ this on a test Odoo database rather than your main database.
|
||||
Run a test transaction from Odoo using the sandbox personal account.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
@ -5,7 +5,7 @@ Razorpay
|
||||
`Razorpay <https://razorpay.com/>`_ is an online payments provider established in India and
|
||||
covering more than 100 payment methods.
|
||||
|
||||
.. _payment_acquirers/razorpay/configure_dashboard:
|
||||
.. _payment_providers/razorpay/configure_dashboard:
|
||||
|
||||
Configuration on Razorpay Dashboard
|
||||
===================================
|
||||
@ -23,16 +23,16 @@ Configuration on Razorpay Dashboard
|
||||
checkboxes are ticked.
|
||||
#. Click on :guilabel:`Create Webhook` to finalize the configuration.
|
||||
|
||||
.. _payment_acquirers/razorpay/configure_odoo:
|
||||
.. _payment_providers/razorpay/configure_odoo:
|
||||
|
||||
Configuration on Odoo
|
||||
=====================
|
||||
|
||||
#. :ref:`Navigate to the payment acquirer Razorpay <payment_acquirers/add_new>` and change its
|
||||
#. :ref:`Navigate to the payment provider Razorpay <payment_providers/add_new>` and change its
|
||||
state to :guilabel:`Enabled`.
|
||||
#. In the :guilabel:`Credentials` tab, fill the :guilabel:`Key Id`, :guilabel:`Key Secret`, and
|
||||
:guilabel:`Webhook Secret` with the values you saved at the step
|
||||
:ref:`payment_acquirers/razorpay/configure_dashboard`.
|
||||
:ref:`payment_providers/razorpay/configure_dashboard`.
|
||||
#. Configure the rest of the options to your liking.
|
||||
|
||||
.. important::
|
||||
@ -44,4 +44,4 @@ Configuration on Odoo
|
||||
to **revoke** it.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
@ -9,7 +9,7 @@ Configuration
|
||||
=============
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
- :ref:`payment_providers/add_new`
|
||||
|
||||
Credentials tab
|
||||
---------------
|
||||
@ -29,4 +29,4 @@ You can copy your credentials from your SIPS environment info documentation, in
|
||||
Mode*. We recommend doing this on a test Odoo database, rather than on your main database.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
@ -9,7 +9,7 @@ Link your Stripe Account with Odoo
|
||||
==================================
|
||||
|
||||
.. seealso::
|
||||
- :ref:`payment_acquirers/add_new`
|
||||
- :ref:`payment_providers/add_new`
|
||||
|
||||
The method to acquire your credentials depends on your hosting type:
|
||||
|
||||
@ -21,14 +21,14 @@ The method to acquire your credentials depends on your hosting type:
|
||||
#. Fill in the requested information and submit the form.
|
||||
#. Confirm your email address when Stripe sends you a confirmation email.
|
||||
#. At the end of the process, you are redirected to Odoo. If you submitted all the requested
|
||||
information, you are all set and your payment acquirer is enabled.
|
||||
information, you are all set and your payment provider is enabled.
|
||||
#. You can continue to :ref:`stripe/local-payment-methods`.
|
||||
|
||||
.. tip::
|
||||
To use your own API keys, :ref:`activate the Developer mode <developer-mode>` and
|
||||
:ref:`enable Stripe manually <payment_acquirers/add_new>`. You can then :ref:`Fill in your
|
||||
:ref:`enable Stripe manually <payment_providers/add_new>`. You can then :ref:`Fill in your
|
||||
credentials <stripe/api-keys>`, :ref:`generate a webhook <stripe/webhook>` and enable the
|
||||
payment acquirer.
|
||||
payment provider.
|
||||
|
||||
.. group-tab:: Odoo.sh or On-premise
|
||||
|
||||
@ -36,15 +36,15 @@ The method to acquire your credentials depends on your hosting type:
|
||||
payments* button on the onboarding banner.
|
||||
#. Fill in the requested information and submit the form.
|
||||
#. Confirm your email address when Stripe sends you a confirmation email.
|
||||
#. At the end of the process, you are redirected to the payment acquirer **Stripe** on Odoo.
|
||||
#. At the end of the process, you are redirected to the payment provider **Stripe** on Odoo.
|
||||
#. :ref:`Fill in your credentials <stripe/api-keys>`.
|
||||
#. :ref:`Generate a webhook <stripe/webhook>`.
|
||||
#. Enable the payment acquirer.
|
||||
#. Enable the payment provider.
|
||||
#. You are all set and can continue to :ref:`stripe/local-payment-methods`.
|
||||
|
||||
.. tip::
|
||||
To connect your Stripe account after the onboarding is already completed, go to
|
||||
:menuselection:`Accounting --> Configuration --> Payment Acquirers --> Stripe` and click on the
|
||||
:menuselection:`Accounting --> Configuration --> Payment Providers --> Stripe` and click on the
|
||||
*Connect Stripe* button.
|
||||
|
||||
.. important::
|
||||
@ -126,7 +126,7 @@ feature earmarks an amount on the customer's account for a determined period of
|
||||
the payment method used.
|
||||
|
||||
To set it up, enable the :guilabel:`Capture Amount Manually` option on Odoo, as explained in the
|
||||
:ref:`payment acquirers documentation <payment_acquirers/features/manual_capture>`.
|
||||
:ref:`payment providers documentation <payment_providers/features/manual_capture>`.
|
||||
|
||||
.. warning::
|
||||
When the manual capture feature is activated, your customers are not able to proceed with any
|
||||
@ -137,7 +137,7 @@ To set it up, enable the :guilabel:`Capture Amount Manually` option on Odoo, as
|
||||
interface is still managed as a full capture by Odoo.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
||||
|
||||
.. _stripe/local-payment-methods:
|
||||
|
||||
@ -156,7 +156,7 @@ Odoo supports the following local payment methods:
|
||||
- Przelewy24 (P24)
|
||||
|
||||
To enable some of these local payment methods with Stripe, list them as supported payment icons. To
|
||||
do so, go to :menuselection:`Payment Acquirers --> Stripe --> Configuration` and add the desired
|
||||
do so, go to :menuselection:`Payment Providers --> Stripe --> Configuration` and add the desired
|
||||
payment methods in the **Supported Payment Icons** field. If the desired payment method is already
|
||||
listed, you don't have anything to do.
|
||||
|
||||
@ -175,7 +175,7 @@ Enable express checkout
|
||||
=======================
|
||||
|
||||
.. seealso::
|
||||
:ref:`payment_acquirers/features/express_checkout`
|
||||
:ref:`payment_providers/features/express_checkout`
|
||||
|
||||
After ticking the :guilabel:`Allow Express Checkout` checkbox, **Google Pay** is enabled out of the
|
||||
box, but **Apple Pay** requires extra steps: You must register your web domain with Apple. This can
|
||||
@ -184,7 +184,7 @@ be done either automatically from Odoo, or manually from Stripe.
|
||||
.. tabs::
|
||||
.. tab:: Register automatically from Odoo
|
||||
|
||||
#. Navigate to your payment acquirer and make sure that it is :guilabel:`enabled`.
|
||||
#. Navigate to your payment provider and make sure that it is :guilabel:`enabled`.
|
||||
#. Go to the :guilabel:`Configuration` tab and click on the :guilabel:`Enable Apple Pay`
|
||||
button. A notification shows that the web domain was successfully registered with Apple.
|
||||
|
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 12 KiB |
@ -4,7 +4,7 @@ How to get paid with wire transfers
|
||||
|
||||
**Wire Transfer** is the default payment method available. The aim is providing your customers with
|
||||
your bank details so they can pay on their own. This is very easy to start with but slow and
|
||||
inefficient process-wise. Opt for payment acquirers as soon as you can!
|
||||
inefficient process-wise. Opt for payment providers as soon as you can!
|
||||
|
||||
How to provide customers with payment instructions
|
||||
==================================================
|
||||
@ -36,4 +36,4 @@ check. To do so, just rename *Wire Transfer* or duplicate it.
|
||||
:align: center
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../payment_acquirers`
|
||||
- :doc:`../payment_providers`
|
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 22 KiB |
Before Width: | Height: | Size: 37 KiB After Width: | Height: | Size: 37 KiB |
Before Width: | Height: | Size: 32 KiB After Width: | Height: | Size: 32 KiB |
@ -19,12 +19,12 @@ feature.
|
||||
:class: img-thumbnail
|
||||
:alt: How to enable online payment on Odoo Sales?
|
||||
|
||||
There, you will have direct access to the **Payment Acquirers** page. It will allow you to select
|
||||
and configure your acquirers of choice. Before creating or modifying a payment acquirer, be sure to
|
||||
check out our documentation about how to be paid with payment acquirers such as
|
||||
:doc:`/applications/finance/payment_acquirers/paypal`,
|
||||
:doc:`/applications/finance/payment_acquirers/authorize`, and others in the
|
||||
:doc:`/applications/finance/payment_acquirers` documentation.
|
||||
There, you will have direct access to the **Payment Providers** page. It will allow you to select
|
||||
and configure your providers of choice. Before creating or modifying a payment provider, be sure to
|
||||
check out our documentation about how to be paid with payment providers such as
|
||||
:doc:`/applications/finance/payment_providers/paypal`,
|
||||
:doc:`/applications/finance/payment_providers/authorize`, and others in the
|
||||
:doc:`/applications/finance/payment_providers` documentation.
|
||||
|
||||
.. note::
|
||||
If you are familiar with this documentation: :doc:`quote_template`; you
|
||||
@ -48,8 +48,8 @@ possibilities to make their online payments. For example:
|
||||
|
||||
.. seealso::
|
||||
- :doc:`quote_template`
|
||||
- :doc:`/applications/finance/payment_acquirers`
|
||||
- :doc:`/applications/finance/payment_acquirers/paypal`
|
||||
- :doc:`/applications/finance/payment_acquirers/authorize`
|
||||
- :doc:`/applications/finance/payment_providers`
|
||||
- :doc:`/applications/finance/payment_providers/paypal`
|
||||
- :doc:`/applications/finance/payment_providers/authorize`
|
||||
|
||||
|
||||
|
@ -7,7 +7,7 @@ Get paid
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
shopper_experience/payment_acquirer
|
||||
shopper_experience/payment_providers
|
||||
shopper_experience/portal
|
||||
|
||||
|
||||
|
@ -1,12 +1,12 @@
|
||||
=========================================
|
||||
Manage orders paid with Payment Acquirers
|
||||
Manage orders paid with Payment Providers
|
||||
=========================================
|
||||
|
||||
The moment a payment is officially authorized by a Payment Acquirer, Odoo *automatically* confirms
|
||||
The moment a payment is officially authorized by a Payment Provider, Odoo *automatically* confirms
|
||||
the order, which triggers the delivery. And, if you invoice based on ordered quantities, you are
|
||||
requested to invoice the order, as well.
|
||||
|
||||
Let’s take a closer look at how to manage orders paid with Payment Acquirers.
|
||||
Let’s take a closer look at how to manage orders paid with Payment Providers.
|
||||
|
||||
Checking the status of a payment
|
||||
================================
|
||||
@ -17,7 +17,7 @@ click on the order you wish to check on.
|
||||
Once you are on the Sales Order page, you will find the payment is confirmed with an automatic note
|
||||
in the *Chatter*.
|
||||
|
||||
.. image:: payment_acquirer/chatter-transaction.png
|
||||
.. image:: payment_providers/chatter-transaction.png
|
||||
:align: center
|
||||
:alt: payment is confirmed in the chatter of sales order
|
||||
|
||||
@ -25,7 +25,7 @@ If the user decides to create an invoice, the payment is directly reconciled. Th
|
||||
the *Chatter* includes a link to the Payment entry, which contains various details about the
|
||||
transaction, along with a link to the related Journal Entry.
|
||||
|
||||
.. image:: payment_acquirer/transaction-info.png
|
||||
.. image:: payment_providers/transaction-info.png
|
||||
:align: center
|
||||
:alt: page with details surrounding the specific transaction
|
||||
|
||||
@ -46,17 +46,17 @@ To do automatically generate invoices at order:
|
||||
- Then, under the **Invoicing Policy** option, select *Invoice what is ordered*.
|
||||
- Then activate *Automatic Invoices* and *Save*.
|
||||
|
||||
.. image:: payment_acquirer/automatic-invoice.png
|
||||
.. image:: payment_providers/automatic-invoice.png
|
||||
:align: center
|
||||
:alt: example of automatic invoice
|
||||
|
||||
Capture payment after the delivery
|
||||
==================================
|
||||
|
||||
If the acquirer handling the payment is configured to capture amounts manually, the order is
|
||||
If the provider handling the payment is configured to capture amounts manually, the order is
|
||||
confirmed, but the amount is kept on hold. Once the delivery is processed, you can capture the
|
||||
payment from the related Sales Order.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../finance/payment_acquirers`
|
||||
- :ref:`Payment Acquirers: Place a hold on a card <payment_acquirers/features/manual_capture>`
|
||||
- :doc:`../../../finance/payment_providers`
|
||||
- :ref:`Payment Providers: Place a hold on a card <payment_providers/features/manual_capture>`
|
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 21 KiB |
Before Width: | Height: | Size: 22 KiB After Width: | Height: | Size: 22 KiB |
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
@ -276,11 +276,11 @@ Leaving the field empty means that you make it work in all websites if
|
||||
*Selectable* is selected. Otherwise, it makes it only available for
|
||||
backend operations of Sales and Point of Sale applications.
|
||||
|
||||
Payment Acquirers and Delivery Methods
|
||||
Payment Providers and Delivery Methods
|
||||
--------------------------------------
|
||||
|
||||
By default, published payment acquirers and delivery methods are deployed in all websites.
|
||||
You could already use specific payment acquirers per country using Geo
|
||||
By default, published payment providers and delivery methods are deployed in all websites.
|
||||
You could already use specific payment providers per country using Geo
|
||||
IP by defining countries in their configuration. Now you can also do it
|
||||
per website by filling in the *Website* field.
|
||||
|
||||
|
@ -0,0 +1,21 @@
|
||||
# applications/finance
|
||||
|
||||
applications/finance/payment_acquirers.rst applications/finance/payment_providers.rst # /payment_acquirers -> /payment_providers
|
||||
applications/finance/payment_acquirers/adyen.rst applications/finance/payment_providers/adyen.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/alipay.rst applications/finance/payment_providers/alipay.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/amazon_payment_services.rst applications/finance/payment_providers/amazon_payment_services.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/asiapay.rst applications/finance/payment_providers/asiapay.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/authorize.rst applications/finance/payment_providers/authorize.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/buckaroo.rst applications/finance/payment_providers/buckaroo.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/flutterwave.rst applications/finance/payment_providers/flutterwave.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/mercado_pago.rst applications/finance/payment_providers/mercado_pago.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/mollie.rst applications/finance/payment_providers/mollie.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/ogone.rst applications/finance/payment_providers/ogone.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/paypal.rst applications/finance/payment_providers/paypal.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/sips.rst applications/finance/payment_providers/sips.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/stripe.rst applications/finance/payment_providers/stripe.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
applications/finance/payment_acquirers/wire_transfer.rst applications/finance/payment_providers/wire_transfer.rst # /payment_acquirers/* -> /payment_providers/*
|
||||
|
||||
# applications/websites
|
||||
|
||||
applications/websites/ecommerce/shopper_experience/payment_acquirer.rst applications/websites/ecommerce/shopper_experience/payment_providers.rst # payment_acquirer -> payment_providers
|