Compare commits
7 Commits
master-aut
...
master-ama
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
70e1dac884 |
[REM] sale_amazon: update not necessary anymore
task-2694222 |
||
|
|
4837aa7eef |
[ADD] accounting/l10n: new egyptian localization and einvoicing section
task-id 2858349
closes odoo/documentation#2148
X-original-commit:
|
||
|
|
75368f52e8 |
[IMP] accounting: add note about bank sync not available for trial db
Added a note to specify that bank synchronization is not available on trial databases
closes odoo/documentation#2138
X-original-commit:
|
||
|
|
646fc412d0 |
[FIX] homepage: fix the link to the external API page
The page was moved from odoo.rst to external_api.rst with commit |
||
|
|
235bcf85f2 |
[IMP] maintain: add note in hosting changes (on-premise to online)
task-id 2869953
closes odoo/documentation#2129
X-original-commit:
|
||
|
|
e8e75d4175 |
[IMP] payment_acquirers: explain the different additional features
task-2862636
closes odoo/documentation#2121
X-original-commit:
|
||
|
|
869d8d1961 |
[IMP] general/payment_acquirers: authorize support refund from odoo
Add 'x' to make evident that Authorize.net supports refunds directly from odoo. Task - 2712287 Task (on payment) - 2678757 closes odoo/documentation#2091 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
|
|
@@ -11,8 +11,6 @@ Depending on the platforms, you have to do it by yourself or contact our support
|
|||
From on-premises to Odoo Online
|
||||
===============================
|
||||
|
||||
.. warning:: Odoo Online is not compatible with **non-standard apps**.
|
||||
|
||||
1. Create a :ref:`duplicate <duplicate_premise>` of your database: in this duplicate, uninstall all the **non-standard apps**.
|
||||
2. Grab a "dump with filestore" of your database by using the Database Manager.
|
||||
3. **If you have time constraints, contact us earlier to schedule the transfer.**
|
||||
|
|
@@ -20,6 +18,11 @@ From on-premises to Odoo Online
|
|||
5. We will make sure your database is compatible and upload it to our cloud. In case of technical issues, we will get in touch with you.
|
||||
6. It's done!
|
||||
|
||||
.. important::
|
||||
- Odoo Online is not compatible with **non-standard apps**.
|
||||
- The database you are moving to Odoo Online must be in a :doc:`supported version
|
||||
<supported_versions>`.
|
||||
|
||||
From on-premises to Odoo.sh
|
||||
===========================
|
||||
|
||||
|
|
|
|||
|
|
@@ -21,6 +21,9 @@ To connect to the banks, Odoo uses multiple web-services:
|
|||
- **Salt Edge**: Europe (:doc:`more information <saltedge>`)
|
||||
- **Ponto**: Europe (:doc:`more information <ponto>`)
|
||||
|
||||
.. important::
|
||||
- Bank synchronization is not available for trial databases.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
|
|
|
|||
|
|
@@ -12,6 +12,7 @@ Localizations
|
|||
localizations/chile
|
||||
localizations/colombia
|
||||
localizations/colombia_ES
|
||||
localizations/egypt
|
||||
localizations/france
|
||||
localizations/germany
|
||||
localizations/indonesia
|
||||
|
|
|
|||
|
|
@@ -0,0 +1,241 @@
|
|||
=====
|
||||
Egypt
|
||||
=====
|
||||
|
||||
.. _egypt/installation:
|
||||
|
||||
Installation
|
||||
============
|
||||
|
||||
:ref:`Install <general/install>` the following modules to get all the features of the Egyptian
|
||||
localization:
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
|
||||
* - Name
|
||||
- Technical name
|
||||
- Description
|
||||
* - :guilabel:`Egypt - Accounting`
|
||||
- ``l10n_eg``
|
||||
- Default :doc:`fiscal localization package <../overview/fiscal_localization_packages>`
|
||||
* - :guilabel:`Egyptian E-invoice Integration`
|
||||
- ``l10n_eg_edi_eta``
|
||||
- :ref:`Egyptian Tax Authority (ETA) e-invoicing integration <egypt/e-invoicing>`
|
||||
|
||||
.. _egypt/e-invoicing:
|
||||
|
||||
Egyptian e-invoicing
|
||||
====================
|
||||
|
||||
Odoo is compliant with the **Egyptian Tax Authority (ETA) e-invoicing** requirements.
|
||||
|
||||
.. important::
|
||||
Egyptian e-invoicing is available from Odoo 15.0. If needed, :doc:`upgrade
|
||||
</administration/upgrade>` your database.
|
||||
|
||||
.. seealso::
|
||||
- `Video: Egypt E-invoicing <https://www.youtube.com/watch?v=NXuBPLR4pVw>`_
|
||||
- :doc:`/administration/upgrade`
|
||||
|
||||
.. _egypt/e-invoicing-eta-portal:
|
||||
|
||||
Register Odoo on your ETA portal
|
||||
--------------------------------
|
||||
|
||||
You must register your Odoo ERP system on your ETA portal to get your API credentials. You need
|
||||
these codes to :ref:`configure your Odoo Accounting app <egypt/e-invoicing-configuration>`.
|
||||
|
||||
Access your company profile on the ETA portal by clicking on :guilabel:`View Taxpayer Profile`.
|
||||
|
||||
.. image:: egypt/taxpayer-profile.png
|
||||
:align: center
|
||||
:alt: Clicking on "View Taxpayer Profile" on an ETA invoicing portal
|
||||
|
||||
Next, go to the :guilabel:`Representatives` section and then click on :guilabel:`Register ERP`.
|
||||
Fill out the :guilabel:`ERP Name` (e.g., ``Odoo``) and leave the other fields empty.
|
||||
|
||||
.. image:: egypt/add-erp-system.png
|
||||
:align: center
|
||||
:alt: Filling out of the form to register an ERP system on the ETA portal.
|
||||
|
||||
Once successfully registered, the website displays your API credentials:
|
||||
|
||||
- Client ID
|
||||
- Client Secret 1
|
||||
- Client Secret 2
|
||||
|
||||
.. note::
|
||||
- ETA should give you a username and a password to access their online portal.
|
||||
- Ask ETA to provide you with preproduction portal access as well.
|
||||
- These codes are confidential and should be stored safely.
|
||||
|
||||
.. _egypt/e-invoicing-configuration:
|
||||
|
||||
Configuration on Odoo
|
||||
---------------------
|
||||
|
||||
To connect your Odoo database to your ETA portal account, go to :menuselection:`Accounting -->
|
||||
Configuration --> Settings --> ETA E-Invoicing Settings`, and set the :guilabel:`ETA Client ID` and
|
||||
:guilabel:`ETA Secret` that you retrieved when you :ref:`registered Odoo on your ETA portal
|
||||
<egypt/e-invoicing-eta-portal>`. Set an invoicing threshold if needed.
|
||||
|
||||
.. image:: egypt/eta-api-integration.png
|
||||
:align: center
|
||||
:alt: Configuration of the ETA E-Invoicing credentials in Odoo Accounting
|
||||
|
||||
.. important::
|
||||
- **Test on your preproduction portal** before starting to issue real invoices on the production
|
||||
ETA portal.
|
||||
- **Credentials** for preproduction and production environments are different. Make sure to
|
||||
update them on Odoo when you move from one environment to another.
|
||||
- If not done yet, fill out your company details with your company's full address, country, and
|
||||
Tax ID.
|
||||
|
||||
.. _egypt/e-invoicing-eta-codes:
|
||||
|
||||
ETA codes
|
||||
~~~~~~~~~
|
||||
|
||||
E-invoicing works with a set of codes provided by the ETA. You can use the `ETA documentation
|
||||
<https://sdk.preprod.invoicing.eta.gov.eg/codes/>`_ to code your business attributes.
|
||||
|
||||
Most of these codes are handled automatically by Odoo, provided that your :ref:`branches
|
||||
<egypt/e-invoicing-branches>`, :ref:`customers <egypt/e-invoicing-customers>`, and :ref:`products
|
||||
<egypt/e-invoicing-products>` are correctly configured.
|
||||
|
||||
- Company Information:
|
||||
|
||||
- Company Tax ID
|
||||
- | Branch ID
|
||||
| If you have only one branch, use ``0`` as the branch code.
|
||||
- Activity type Code
|
||||
|
||||
- Other Information:
|
||||
|
||||
- | Product Codes
|
||||
| Your company's products should be coded and matched with their **GS1** or **EGS** codes.
|
||||
- | Tax Codes
|
||||
| Most of the taxes codes are already configured on Odoo in the :guilabel:`ETA Code (Egypt)`
|
||||
field. We advise you to make sure these codes match your company's taxes.
|
||||
|
||||
.. seealso::
|
||||
- `Egyptian eInvoicing & eReceipt SDK - Code Tables
|
||||
<https://sdk.preprod.invoicing.eta.gov.eg/codes/>`_
|
||||
- :doc:`../../taxation/taxes/taxes`
|
||||
|
||||
.. _egypt/e-invoicing-branches:
|
||||
|
||||
Branches
|
||||
~~~~~~~~
|
||||
|
||||
Create a contact and a journal for each branch of your company and configure its ETA settings.
|
||||
|
||||
To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, then click on
|
||||
:guilabel:`Create`.
|
||||
|
||||
Name the journal according to your company's branch and set the :guilabel:`Type` as
|
||||
:guilabel:`Sales`. Next, open the :menuselection:`Advanced Settings` tab and fill out the
|
||||
:guilabel:`Egyptian ETA settings` section:
|
||||
|
||||
- In the :guilabel:`Branch` field, select the branch's contact or create it.
|
||||
- Set the :guilabel:`ETA Activity Code`.
|
||||
- Set the :guilabel:`ETA Branch ID` (use ``0`` if you have one branch only).
|
||||
|
||||
.. image:: egypt/branch-journal.png
|
||||
:align: center
|
||||
:alt: Sales journal configuration of an Egyptian company's branch
|
||||
|
||||
.. important::
|
||||
The contact selected in the :guilabel:`Branch` field must be set as a :guilabel:`Company`
|
||||
(**not** as an :guilabel:`Individual`), and the :guilabel:`Address` and :guilabel:`Tax ID` fields
|
||||
must be filled out.
|
||||
|
||||
.. _egypt/e-invoicing-customers:
|
||||
|
||||
Customers
|
||||
~~~~~~~~~
|
||||
|
||||
Make sure your customers' contact forms are correctly filled out so your e-invoices are valid:
|
||||
|
||||
- contact type: :guilabel:`Individual`: or :guilabel:`Company`:
|
||||
- :guilabel:`Country`:
|
||||
- :guilabel:`Tax ID`: Tax ID or Company registry for companies. National ID for individuals.
|
||||
|
||||
.. note::
|
||||
You can edit your customers' contact forms by going to :menuselection:`Accounting --> Customers
|
||||
--> Customers`.
|
||||
|
||||
.. _egypt/e-invoicing-products:
|
||||
|
||||
Products
|
||||
~~~~~~~~
|
||||
|
||||
Make sure your products are correctly configured so your e-invoices are valid:
|
||||
|
||||
- :guilabel:`Product Type`: storable products, consumables, or services.
|
||||
- :guilabel:`Unit of Measure`: if you also use Odoo Inventory and have enabled :doc:`Units of
|
||||
Measure </applications/inventory_and_mrp/inventory/management/products/uom>`.
|
||||
- :guilabel:`Barcode`: **GS1** or **EGS** barcode
|
||||
- :guilabel:`ETA Item code` (under the :menuselection:`Accounting` tab): if the barcode doesn't
|
||||
match your ETA item code.
|
||||
|
||||
.. note::
|
||||
You can edit your products by going to :menuselection:`Accounting --> Customers --> Products`.
|
||||
|
||||
.. _egypt/e-invoicing-usb-authentication:
|
||||
|
||||
USB authentication
|
||||
------------------
|
||||
|
||||
Each person who needs to electronically sign invoices needs a specific USB key to authenticate and
|
||||
send invoices to the ETA portal through an ERP.
|
||||
|
||||
.. note::
|
||||
You can contact the :abbr:`ETA (Egyptian Tax Authority)` or `Egypt Trust
|
||||
<https://www.egypttrust.com/>`_ to get these USB keys.
|
||||
|
||||
.. _egypt/e-invoicing-local-proxy:
|
||||
|
||||
Install Odoo as a local proxy on your computer
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
An Odoo local server works as a bridge between your computer and your Odoo database hosted online.
|
||||
|
||||
Download the Odoo Community installer from the page https://www.odoo.com/page/download and start the
|
||||
installation on your computer.
|
||||
|
||||
Select :guilabel:`Local Proxy Mode` as the type of install.
|
||||
|
||||
.. image:: egypt/install-odoo-local-proxy.png
|
||||
:align: center
|
||||
:alt: Selection of "Local Proxy Mode" during the installation of Odoo Community.
|
||||
|
||||
.. note::
|
||||
This installation of Odoo only works as a server and does not install any Odoo apps on your
|
||||
computer.
|
||||
|
||||
Once the installation is complete, the installer displays your **access token** for the Odoo Local
|
||||
Proxy. Copy the token and save it in a safe place for later use.
|
||||
|
||||
.. seealso::
|
||||
- `Odoo: Download Odoo <https://www.odoo.com/page/download>`_
|
||||
- :doc:`/administration/install/install`
|
||||
|
||||
.. _egypt/e-invoicing-usb-configuration:
|
||||
|
||||
Configure the USB key
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Once the local proxy server is installed on your computer, you can link it with your Odoo database.
|
||||
|
||||
#. Go to :menuselection:`Accounting --> Configurations --> Thumb Drive` and click on
|
||||
:guilabel:`Create`.
|
||||
#. Input a :guilabel:`Company` name, the :guilabel:`ETA USB Pin` given to you by your USB key
|
||||
provider, and the :guilabel:`Access Token` provided at the end of the :ref:`local proxy
|
||||
installation <egypt/e-invoicing-local-proxy>`, then click on :guilabel:`Save`.
|
||||
#. Click on :guilabel:`Get certificate`.
|
||||
|
||||
.. image:: egypt/thumb-drive.png
|
||||
:align: center
|
||||
:alt: Creating a new thumb drive for the e-invoicing of an egyptian company.
|
||||
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 21 KiB |
|
After Width: | Height: | Size: 5.6 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 6.5 KiB |
|
|
@@ -53,46 +53,76 @@ the payments that go directly on the bank account and follow the usual reconcili
|
|||
Online payment acquirers
|
||||
------------------------
|
||||
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| | Payment flow | Save cards | Capture amount | Refund |
|
||||
| | | | manually | from Odoo |
|
||||
+==================================+=====================+============+================+===========+
|
||||
| :doc:`Adyen | Payment from Odoo | |V| | |V| | |V| |
|
||||
| <payment_acquirers/adyen>` | | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| :doc:`Alipay | Redirection to the | | | |
|
||||
| <payment_acquirers/alipay>` | acquirer website | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| :doc:`Authorize.Net | Payment from Odoo | |V| | |V| | |
|
||||
| <payment_acquirers/authorize>` | | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| :doc:`Buckaroo | Redirection to the | | | |
|
||||
| <payment_acquirers/buckaroo>` | acquirer website | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| :doc:`Flutterwave | Redirection to the | |V| | | |
|
||||
| <payment_acquirers/flutterwave>` | acquirer website | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| :doc:`Mollie | Redirection to the | | | |
|
||||
| <payment_acquirers/mollie>` | acquirer website | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| :doc:`Ogone | Redirection to the | |V| | | |
|
||||
| <payment_acquirers/ogone>` | acquirer website | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| :doc:`PayPal | Redirection to the | | | |
|
||||
| <payment_acquirers/paypal>` | acquirer website | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| PayU Latam | Redirection to the | | | |
|
||||
| | acquirer website | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| PayUMoney | Redirection to the | | | |
|
||||
| | acquirer website | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| :doc:`SIPS | Redirection to the | | | |
|
||||
| <payment_acquirers/sips>` | acquirer website | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
| :doc:`Stripe | Redirection to the | |V| | |V| | |V| |
|
||||
| <payment_acquirers/stripe>` | acquirer website | | | |
|
||||
+----------------------------------+---------------------+------------+----------------+-----------+
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:stub-columns: 1
|
||||
:widths: auto
|
||||
|
||||
* -
|
||||
- Payment flow
|
||||
- :ref:`Save cards for later <payment_acquirers/features/tokenization>`
|
||||
- :ref:`Manual capture <payment_acquirers/features/manual_capture>`
|
||||
- :ref:`Refunds <payment_acquirers/features/refund>`
|
||||
* - :doc:`Adyen <payment_acquirers/adyen>`
|
||||
- Payment from Odoo
|
||||
- |V|
|
||||
- Full only
|
||||
- Full and partial
|
||||
* - :doc:`Alipay <payment_acquirers/alipay>`
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Authorize.Net <payment_acquirers/authorize>`
|
||||
- Payment from Odoo
|
||||
- |V|
|
||||
- Full only
|
||||
- Full only
|
||||
* - :doc:`Buckaroo <payment_acquirers/buckaroo>`
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Flutterwave <payment_acquirers/flutterwave>`
|
||||
- Payment from the acquirer website
|
||||
- |V|
|
||||
-
|
||||
-
|
||||
* - :doc:`Mollie <payment_acquirers/mollie>`
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Ogone <payment_acquirers/ogone>`
|
||||
- Payment from the acquirer website
|
||||
- |V|
|
||||
-
|
||||
-
|
||||
* - :doc:`PayPal <payment_acquirers/paypal>`
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - PayU Latam
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - PayUMoney
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`SIPS <payment_acquirers/sips>`
|
||||
- Payment from the acquirer website
|
||||
-
|
||||
-
|
||||
-
|
||||
* - :doc:`Stripe <payment_acquirers/stripe>`
|
||||
- Payment from the acquirer website
|
||||
- |V|
|
||||
- Full only
|
||||
- Full and partial
|
||||
|
||||
.. |V| replace:: ✔
|
||||
|
||||
|
|
@@ -116,6 +146,87 @@ Bank payments
|
|||
directly. :doc:`Click here <../finance/accounting/receivables/customer_payments/batch_sdd>` for
|
||||
more information about this payment method.
|
||||
|
||||
.. _payment_acquirers/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
|
||||
features.
|
||||
|
||||
.. _payment_acquirers/features/tokenization:
|
||||
|
||||
Save cards for later
|
||||
--------------------
|
||||
|
||||
If your payment acquirer supports this feature, customers can choose to save their card details as a
|
||||
**payment token** in Odoo. When they do, they will not have to enter their card details again when
|
||||
making a subsequent payment. 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
|
||||
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.
|
||||
|
||||
.. _payment_acquirers/features/manual_capture:
|
||||
|
||||
Manual capture
|
||||
--------------
|
||||
|
||||
If your payment acquirer 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
|
||||
equivalent to a regular cancellation. Capturing payments manually can prove itself useful in many
|
||||
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
|
||||
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
|
||||
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
|
||||
on the :guilabel:`CAPTURE TRANSACTION` button. To release the funds, click on the :guilabel:`VOID
|
||||
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
|
||||
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
|
||||
for the exact reservation duration.
|
||||
- Odoo does not support this feature for all payment acquirers but some allow the manual capture
|
||||
from their website interface.
|
||||
|
||||
.. _payment_acquirers/features/refund:
|
||||
|
||||
Refunds
|
||||
-------
|
||||
|
||||
If your payment acquirer 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
|
||||
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
|
||||
from their website interface.
|
||||
|
||||
.. _payment_acquirers/configuration:
|
||||
|
||||
Configuration
|
||||
|
|
@@ -166,48 +277,6 @@ You can change the payment acquirer's front-end appearance by modifying its name
|
|||
**Displayed as** field and which credit card icons to display under the **Supported Payment Icons**
|
||||
field.
|
||||
|
||||
.. _payment_acquirers/save_cards:
|
||||
|
||||
Save and reuse credit cards
|
||||
***************************
|
||||
|
||||
With the **Save Cards** feature, Odoo can store **Payment Tokens** in your database, which can be
|
||||
used for subsequent payments, without having to reenter the payment details. This is particularly
|
||||
useful for the eCommerce conversion rate and subscriptions' recurring payments.
|
||||
|
||||
.. _payment_acquirers/capture_amount:
|
||||
|
||||
Place a hold on a card
|
||||
**********************
|
||||
|
||||
If you wish to manually capture an amount instead of having an immediate capture, you can enable the
|
||||
manual capture. Capturing payments manually has many advantages:
|
||||
|
||||
- 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 credit card fees in the event of overselling or cancelled orders.
|
||||
|
||||
The **Capture Amount Manually** field is under the **Configuration** tab. If enabled, the funds are
|
||||
reserved for a few days on the customer's card, but not charged yet. Please refer to your acquirer's
|
||||
documentation for the exact reservation duration.
|
||||
|
||||
.. image:: payment_acquirers/capture_manually.png
|
||||
:align: center
|
||||
:alt: Configuration tab on Odoo
|
||||
|
||||
To capture the payment, you must then go to the related sales order or invoice and manually
|
||||
*capture* the funds before its automatic cancellation, or *void the transaction* to unlock the funds
|
||||
from the customer's card.
|
||||
|
||||
.. image:: payment_acquirers/capture.png
|
||||
:align: center
|
||||
:alt: Hold the credit card payment until you capture or revoke it on Odoo
|
||||
|
||||
.. note::
|
||||
Odoo may not yet support the manual capture for all acquirers, but some acquirers allow managing
|
||||
the capture from their interfaces.
|
||||
|
||||
.. _payment_acquirers/countries:
|
||||
|
||||
Countries
|
||||
|
|
|
|||
|
|
@@ -105,7 +105,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/capture_amount>`.
|
||||
:ref:`payment acquirers documentation <payment_acquirers/features/manual_capture>`.
|
||||
|
||||
Then, open your Adyen Merchant Account, go to :menuselection:`Account --> Settings`, and set the
|
||||
**Capture Delay** to **manual**.
|
||||
|
|
|
|||
|
|
@@ -42,8 +42,9 @@ Configuration tab
|
|||
Place a hold on a card
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
With Authorize.net, you can enable the :ref:`manual capture <payment_acquirers/capture_amount>`. If
|
||||
enabled, the funds are reserved for 30 days on the customer's card, but not charged yet.
|
||||
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
|
||||
customer's card, but not charged yet.
|
||||
|
||||
.. warning::
|
||||
After **30 days**, the transaction is **voided automatically** by Authorize.net.
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 4.7 KiB |
|
Before Width: | Height: | Size: 10 KiB |
|
|
@@ -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/capture_amount>`.
|
||||
:ref:`payment acquirers documentation <payment_acquirers/features/manual_capture>`.
|
||||
|
||||
.. warning::
|
||||
When the manual capture feature is activated, your customers are not able to proceed with any
|
||||
|
|
|
|||
|
|
@@ -9,5 +9,4 @@ Amazon Connector
|
|||
|
||||
amazon_connector/features
|
||||
amazon_connector/setup
|
||||
amazon_connector/manage
|
||||
amazon_connector/update
|
||||
amazon_connector/manage
|
||||
|
|
@@ -1,60 +0,0 @@
|
|||
=============================================
|
||||
Install the Amazon Selling Partner API Update
|
||||
=============================================
|
||||
|
||||
Starting July 2022, due to a change in Amazon's API, the Amazon Connector needs to be updated to
|
||||
continue to exchange information with Amazon. This also makes it easier for you to set up the
|
||||
Connector.
|
||||
|
||||
.. note::
|
||||
If your Odoo database is created after the update was released, the update module is installed
|
||||
automatically. To check if this module is already installed, go to :guilabel:`Apps`, remove the
|
||||
``Apps`` filter and search for ``Amazon``. If the module :guilabel:`Amazon/Selling Partner API
|
||||
Patch` is present and marked as installed, your Odoo database is already up-to-date and you can
|
||||
proceed with the :doc:`setup <setup>` step of the Amazon Connector.
|
||||
|
||||
Update Odoo to the latest release
|
||||
=================================
|
||||
|
||||
The new authentication mechanism is made available through a new Odoo module; to
|
||||
be able to install it, you must make sure that your Odoo source code is up-to-date.
|
||||
|
||||
If you use Odoo on Odoo.com or Odoo.sh platform, your code is already up-to-date and
|
||||
you can proceed to the next step.
|
||||
|
||||
If you use Odoo with an on-premise setup or through a partner, then you must update
|
||||
your installation as detailed in
|
||||
:doc:`this documentation page </administration/maintain/update>`
|
||||
or by contacting your integrating partner.
|
||||
|
||||
Update the list of available modules
|
||||
====================================
|
||||
|
||||
New modules must be *discovered* by your Odoo instance to be available in the **Apps**
|
||||
menu.
|
||||
|
||||
To do so, activate the :ref:`developer mode <developer-mode>`, and go to :menuselection:`Apps -->
|
||||
Update Apps List`. A wizard will ask for confirmation.
|
||||
|
||||
Install the Amazon/Selling Partner API Patch
|
||||
============================================
|
||||
|
||||
.. warning::
|
||||
You should never install new modules in your production database without first testing them in a
|
||||
duplicate or staging environment. For Odoo.com customers, a duplicate database can be created
|
||||
from the database management page. For Odoo.sh users, you should use a staging or duplicate
|
||||
database. For on-premise users, you should use a staging environment---contact your integrating
|
||||
partner for more information regarding how to test a new module in your particular setup.
|
||||
|
||||
The module should now be available in your :guilabel:`Apps` menu. Remove the ``Apps`` filter and
|
||||
search for ``Amazon``; the module :guilabel:`Amazon/Selling Partner API Patch` should be available
|
||||
for installation. If you cannot find the module after having updated the list of available modules,
|
||||
it means your Odoo source code is not up-to-date; refer to step one of this page.
|
||||
|
||||
Once the module is installed, link your Amazon account by following the instructions on the
|
||||
:doc:`setup <setup>` page.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`features`
|
||||
- :doc:`setup`
|
||||
- :doc:`manage`
|
||||
|
|
@@ -59,4 +59,4 @@ payment from the related Sales Order.
|
|||
|
||||
.. seealso::
|
||||
- :doc:`../../../finance/payment_acquirers`
|
||||
- :ref:`Payment Acquirers: Place a hold on a card <payment_acquirers/capture_amount>`
|
||||
- :ref:`Payment Acquirers: Place a hold on a card <payment_acquirers/features/manual_capture>`
|
||||
|
|
|
|||
|
|
@@ -86,7 +86,7 @@
|
|||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="{{ pathto('developer/misc/api/odoo') }}" class="stretched-link">
|
||||
<a href="{{ pathto('developer/misc/api/external_api') }}" class="stretched-link">
|
||||
{{ _("External API") }}
|
||||
</a>
|
||||
</li>
|
||||
|
|
|
|||