[REF][MOV] documentation apocalypse
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
@@ -0,0 +1,77 @@
|
||||
==================================
|
||||
How to get paid with Authorize.Net
|
||||
==================================
|
||||
|
||||
Authorize.Net is one of the most popular eCommerce payment platforms in North America.
|
||||
Unlike most of the other payment acquirers compatible with Odoo,
|
||||
Authorize.Net can be used as `payment gateway <https://www.authorize.net/solutions/merchantsolutions/pricing/?p=gwo>`__ only.
|
||||
That way you can use the `payment processor or merchant <https://www.authorize.net/partners/resellerprogram/processorlist/>`__ that you like.
|
||||
|
||||
|
||||
Create an Authorize.Net account
|
||||
===============================
|
||||
|
||||
* Create an `Authorize.Net account <https://www.authorize.net>`__
|
||||
by clicking 'Get Started'.
|
||||
* In the pricing page, press *Sign up now* if you want to use Authorize.net as
|
||||
both payment gateway and merchant. If you want to use your own merchant, press
|
||||
the related option.
|
||||
|
||||
.. image:: media/authorize01.png
|
||||
:align: center
|
||||
|
||||
* Go through the registration steps.
|
||||
* The account is set as a test account by default. You can use this test
|
||||
account to process a test transaction from Odoo.
|
||||
* Once ready, switch to **Production** mode.
|
||||
|
||||
|
||||
Set up Odoo
|
||||
===========
|
||||
* Activate Authorize.Net in Odoo from :menuselection:`Website or Sales or Accounting
|
||||
--> Settings --> Payment Acquirers`.
|
||||
* Enter both your **Login ID**
|
||||
and your **API Transaction Key**.
|
||||
|
||||
.. image:: media/authorize02.png
|
||||
:align: center
|
||||
|
||||
To get those credentials in Authorize.Net, you can rely on
|
||||
*API Login ID and Transaction Key* video of
|
||||
`Authorize.Net Video Tutorials <https://www.authorize.net/videos/>`__.
|
||||
Such videos give meaningful insights about how to set up your
|
||||
Authorize.Net account according to your needs.
|
||||
|
||||
|
||||
Go live
|
||||
=======
|
||||
Your configuration is now ready!
|
||||
You can make Authorize.Net visible on your merchant interface
|
||||
and activate the **Production** mode.
|
||||
|
||||
.. image:: media/paypal_live.png
|
||||
:align: center
|
||||
|
||||
.. note:: Credentials provided by Authorize.net are different for both
|
||||
test and production mode. Don't forget to update them in Odoo when you
|
||||
turn on the production mode.
|
||||
|
||||
|
||||
Assess Authorize.Net as payment solution
|
||||
========================================
|
||||
You can test and assess Authorize.Net for free by creating a `developer account <https://developer.authorize.net>`__.
|
||||
|
||||
Once the account created you receive sandbox credentials.
|
||||
Enter them in Odoo as explained here above and make sure
|
||||
you are still in *Test* mode.
|
||||
|
||||
You can also log in to `Authorize.Net sandbox platform <https://sandbox.authorize.net/>`__
|
||||
to configure your sandbox account.
|
||||
|
||||
To perform ficticious transactions you can use fake card numbers
|
||||
provided in the `Authorize.Net Testing Guide <https://developer.authorize.net/hello_world/testing_guide/>`__.
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`payment`
|
||||
* :doc:`payment_acquirer`
|
||||
|
After Width: | Height: | Size: 5.7 KiB |
|
After Width: | Height: | Size: 3.0 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 22 KiB |
|
After Width: | Height: | Size: 37 KiB |
|
After Width: | Height: | Size: 32 KiB |
|
After Width: | Height: | Size: 34 KiB |
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 24 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 58 KiB |
|
After Width: | Height: | Size: 9.9 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 3.7 KiB |
|
After Width: | Height: | Size: 5.2 KiB |
|
After Width: | Height: | Size: 3.9 KiB |
|
After Width: | Height: | Size: 5.1 KiB |
|
After Width: | Height: | Size: 6.1 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 6.3 KiB |
|
After Width: | Height: | Size: 6.4 KiB |
|
After Width: | Height: | Size: 10 KiB |
|
After Width: | Height: | Size: 4.0 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 9.4 KiB |
|
After Width: | Height: | Size: 7.9 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 9.8 KiB |
|
After Width: | Height: | Size: 34 KiB |
|
After Width: | Height: | Size: 5.3 KiB |
|
After Width: | Height: | Size: 25 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 10 KiB |
|
After Width: | Height: | Size: 7.5 KiB |
|
After Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 4.7 KiB |
|
After Width: | Height: | Size: 35 KiB |
|
After Width: | Height: | Size: 18 KiB |
@@ -0,0 +1,111 @@
|
||||
======================================
|
||||
How to get paid with payment acquirers
|
||||
======================================
|
||||
|
||||
Odoo embeds several payment methods to get paid on eCommerce, Sales
|
||||
and Invoicing apps.
|
||||
|
||||
|
||||
What are the payment methods available
|
||||
======================================
|
||||
|
||||
Wire transfer
|
||||
-------------
|
||||
|
||||
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 via their bank.
|
||||
This is very easy to start with but slow and inefficient process-wise.
|
||||
Opt for online acquirers as soon as you can!
|
||||
|
||||
Payment acquirers
|
||||
-----------------
|
||||
|
||||
Redirect your customers to payment platforms to collect money effortless
|
||||
and track the payment status (call-back).
|
||||
Odoo supports more and more platforms over time:
|
||||
|
||||
* `Paypal <paypal.html>`__
|
||||
* Ingenico
|
||||
* Authorize.net
|
||||
* Adyen
|
||||
* Buckaroo
|
||||
* PayUmoney
|
||||
* Sips
|
||||
* Stripe
|
||||
|
||||
|
||||
How to go live
|
||||
==============
|
||||
|
||||
Once the payment method ready, make it visible in the payment interface
|
||||
and activate the **Production** mode.
|
||||
|
||||
.. image:: media/paypal_live.png
|
||||
:align: center
|
||||
|
||||
|
||||
How to let customers save and reuse credit cards
|
||||
================================================
|
||||
To ease the payment of returning customers, you can let them
|
||||
save and reuse a credit card if they want to.
|
||||
If so, a payment token will be saved in Odoo.
|
||||
This option is available with Ingenico and Authorize.net.
|
||||
|
||||
You can turn this on from the acquirer configuration form.
|
||||
|
||||
.. image:: media/payment_save_card.png
|
||||
:align: center
|
||||
|
||||
|
||||
How to debit credit cards to pay subscriptions
|
||||
==============================================
|
||||
`Odoo Subscription <https://www.odoo.com/page/subscriptions>`__ allows to
|
||||
bill services automatically on a recurring basis.
|
||||
Along with it, you can have an automatic debit of the customer's credit card.
|
||||
|
||||
This option is available with Ingenico and Authorize.net.
|
||||
|
||||
You can turn this on from the acquirer configuration form.
|
||||
|
||||
.. image:: media/payment_recurring.png
|
||||
:align: center
|
||||
|
||||
That way a payment token will be recorded when the customer
|
||||
goes for the subscription and an automatic debit will occur
|
||||
whenever an invoice is issued from the subscription.
|
||||
|
||||
|
||||
How to use other acquirers (advanced)
|
||||
=====================================
|
||||
|
||||
Odoo can submit single payment requests and redirect to any payment acquirer.
|
||||
But there is no call-back, i.e. Odoo doesn't track the transaction status.
|
||||
So you will confirm orders manually once you get paid.
|
||||
|
||||
How to:
|
||||
|
||||
* Switch to developer mode.
|
||||
|
||||
* Take the **Custom** payment method.
|
||||
|
||||
* Set up the payment form (S2S Form Template) as instructed by your payment acquirer.
|
||||
You can start from *default_acquirer_button* that you can duplicate.
|
||||
|
||||
|
||||
Other configurations
|
||||
====================
|
||||
|
||||
Odoo can also be used for more advanced payment processes
|
||||
like installment plans (e.g.
|
||||
`Paypal Installment Plans <https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/installment_buttons>`__).
|
||||
|
||||
Such a customization service is made on-demand by our technical experts
|
||||
based on your own requirements. A business advisor can reach you out for
|
||||
such matter. `Contact us. <https://www.odoo.com/page/contactus>`__
|
||||
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`paypal`
|
||||
* :doc:`wire_transfer`
|
||||
* :doc:`payment_acquirer`
|
||||
@@ -0,0 +1,79 @@
|
||||
===================================================
|
||||
How to manage orders paid with payment acquirers
|
||||
===================================================
|
||||
|
||||
Odoo confirms orders automatically as soon as the payment is authorized
|
||||
by a payment acquirer. This triggers the delivery.
|
||||
If you invoice based on ordered quantities,
|
||||
you are also requested to invoice the order.
|
||||
|
||||
|
||||
What are the payment status
|
||||
===========================
|
||||
At anytime, the salesman can check the transaction status from the order.
|
||||
|
||||
.. image:: media/payment_transaction.png
|
||||
:align: center
|
||||
|
||||
* *Draft*: transaction under processing.
|
||||
|
||||
* *Pending*: the payment acquirer keeps the transaction on hold and you
|
||||
need to authorize it from the acquirer interface.
|
||||
|
||||
* *Authorized*: the payment has been authorized but not yet captured.
|
||||
In Odoo, the order is already confirmed. Once the delivery done, you
|
||||
can capture the amount from the acquirer interface (or from Odoo if you use
|
||||
Authorize.net).
|
||||
|
||||
* *Done*: the payment is authorized and captured. The order has been confirmed.
|
||||
|
||||
* *Error*: an error has occured during the transaction.
|
||||
The customer needs to retry the payment.
|
||||
The order is still in draft.
|
||||
|
||||
* *Cancelled*: when the customer cancels the payment in the payment acquirer form.
|
||||
They are taken back to Odoo in order to modify the order.
|
||||
|
||||
.. note:: Specific messages are provided to your customers for every
|
||||
payment status, when they are redirected to Odoo after the transaction.
|
||||
To edit such messages, go to the *Messages* tab of the payment
|
||||
method.
|
||||
|
||||
|
||||
Auto-validate invoices at order
|
||||
===============================
|
||||
|
||||
When the order is confirmed you can also have an invoice automatically issued
|
||||
and paid. This fully-automated made for businesses that invoice
|
||||
orders straight on.
|
||||
|
||||
.. image:: media/payment_invoice.png
|
||||
:align: center
|
||||
|
||||
.. note:: If you choose this mode you are requested to select a payment journal
|
||||
in order to record payments in your books.
|
||||
This payment is automatically reconcilied with the invoice, marking it as paid.
|
||||
Select your **bank account** if you get paid immediately on your bank account.
|
||||
If you don't you can create a specific journal for the payment acquirer
|
||||
(type = Bank). That way, you can track online payments in an intermediary
|
||||
account of your books until you get paid into your bank account
|
||||
(see `How to register credit card payments <../../accounting/receivables/customer_payments/credit_cards.html>`__).
|
||||
|
||||
|
||||
Capture the payment after the delivery
|
||||
======================================
|
||||
With this mode, the order is confirmed but the amount is kept on hold.
|
||||
Once the delivery processed, you can capture the payment from Odoo.
|
||||
This mode is only available with Authorize.net.
|
||||
|
||||
.. image:: media/payment_capture_mode.png
|
||||
:align: center
|
||||
|
||||
To capture the payment, open the transaction from the order.
|
||||
Then click *Capture Transaction*.
|
||||
|
||||
.. image:: media/payment_capture.png
|
||||
:align: center
|
||||
|
||||
With other payment acquirers, you can manage the capture in
|
||||
their own interfaces, not from Odoo.
|
||||
@@ -0,0 +1,202 @@
|
||||
=============================
|
||||
Configure your Paypal account
|
||||
=============================
|
||||
|
||||
Paypal is available and popular worldwide. It doesn’t charge any
|
||||
subscription fee and creating an account is very easy. That’s why we
|
||||
definitely recommend it for starters in Odoo. It works as a seamless
|
||||
flow where the customer is routed to Paypal website to register the
|
||||
payment.
|
||||
|
||||
Paypal account
|
||||
==============
|
||||
|
||||
A business account is needed to get paid with Paypal. Create a `Paypayl Business Account <https://www.paypal.com/us/merchantsignup/applicationChecklist?signupType=CREATE_NEW_ACCOUNT&productIntentId=wp_standard>`__ or upgrade your Personal account to a Business account. Go to the Paypal settings and click on *Upgrade to a Business account*. Then follow the few configuration steps.
|
||||
|
||||
|
||||
Settings in Paypal
|
||||
==================
|
||||
|
||||
| First, let’s see how to set up your Paypal account in order to build a
|
||||
seamless customer experience with Odoo.
|
||||
| Log in and open the settings. Go to *Products & Services > Website
|
||||
payments* and click *Update* on *Website preferences*.
|
||||
|
||||
.. image:: media/paypal01.png
|
||||
:align: center
|
||||
|
||||
Auto Return
|
||||
-----------
|
||||
|
||||
*Auto Return* automatically redirects your customers to Odoo once the
|
||||
payment is processed. Check *Auto Return* and enter your domain name
|
||||
"/shop/confirmation" as *Return URL* (e.g.
|
||||
https://yourcompany.odoo.com/shop/confirmation).
|
||||
|
||||
This URL is requested in Paypal but not used in practice as Odoo
|
||||
transmits it at each transaction. Don’t worry if you manage several
|
||||
sales channels or Odoo databases.
|
||||
|
||||
.. image:: media/paypal02.png
|
||||
:align: center
|
||||
|
||||
Payment Data Transfer (PDT)
|
||||
---------------------------
|
||||
|
||||
*Payment Data Transfer* delivers the payment confirmation to Odoo as
|
||||
soon as it is processed. Without it, Odoo cannot end the sales flow.
|
||||
This setting must be activated as well. When saving, an *Identity
|
||||
Token* is generated. You will be later requested to enter it in Odoo.
|
||||
|
||||
.. image:: media/paypal03.png
|
||||
:align: center
|
||||
|
||||
Paypal Account Optional
|
||||
|
||||
We advise you to not prompt customers to log in with a Paypal account
|
||||
when they get to pay. Let them pay with debit/credit cards as well, or you might lose some deals. Make sure this setting is turned on.
|
||||
|
||||
.. image:: media/paypal04.png
|
||||
:align: center
|
||||
|
||||
Instant Payment Notification (IPN)
|
||||
----------------------------------
|
||||
|
||||
PDT sends order confirmations once and only once. As a result, your site
|
||||
must be running when it happens; otherwise, it will never receive the
|
||||
message. That’s why we advise to activate the *Instant Payment
|
||||
Notification* (IPN) on top. With IPN, delivery of order confirmations
|
||||
is virtually guaranteed since IPN resends a confirmation until your site acknowledges receipt.
|
||||
|
||||
| To activate IPN, get back to *Website payments* menu and click
|
||||
*Update* in *Instant Payment Notification*.
|
||||
| The *Notification URL* to set is your domain name +
|
||||
“payment/paypal/ipn” (e.g.
|
||||
https://yourcompany.odoo.com/payment/paypal/ipn).
|
||||
|
||||
.. image:: media/paypal05.png
|
||||
:align: center
|
||||
|
||||
Payment Messages Format
|
||||
-----------------------
|
||||
|
||||
If you use accented characters (or anything else than basic Latin characters)
|
||||
for your customer names, addresses... you MUST configure the encoding format of
|
||||
the payment request sent by Odoo to Paypal.
|
||||
|
||||
.. danger::
|
||||
|
||||
If you don't configure this setting, some transactions fail without notice.
|
||||
|
||||
To do so, open:
|
||||
|
||||
* `this page for a test account <https://sandbox.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-language-encoding>`__
|
||||
|
||||
* `this page for a production account <https://www.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-language-encoding>`__
|
||||
|
||||
Then, click *More Options* and set the two default encoding formats as **UTF-8**.
|
||||
|
||||
.. image:: media/paypal07.png
|
||||
:align: center
|
||||
|
||||
.. image:: media/paypal08.png
|
||||
:align: center
|
||||
|
||||
Your Paypal account is ready!
|
||||
|
||||
.. tip:: If you want your customers to pay without creating a Paypal account,
|
||||
**Paypal Account Optional** needs to be turned on.
|
||||
|
||||
.. image:: media/paypal_account_optional.png
|
||||
:align: center
|
||||
|
||||
.. tip:: For Encrypted Website Payments & EWP_SETTINGS error,
|
||||
please check the `paypal documentation. <https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/encryptedwebpayments/#encrypted-website-payments-ewp>`__
|
||||
|
||||
Settings in Odoo
|
||||
================
|
||||
|
||||
Activation
|
||||
----------
|
||||
|
||||
Activate *Paypal* from the config bar of Sales, Invoicing and
|
||||
eCommerce apps, or from the configuration menu of *Payment Acquirers*.
|
||||
|
||||
Credentials
|
||||
-----------
|
||||
|
||||
Odoo requires three Paypal credentials:
|
||||
|
||||
- *Email ID* is your login email address in Paypal.
|
||||
|
||||
- *Merchant ID* can be found in the settings of your Paypal account, in *Profile > About the business*.
|
||||
|
||||
- *Paypal PDT Token* is given in *Website payments* configuration as explained here above.
|
||||
|
||||
.. image:: media/paypal09.png
|
||||
:align: center
|
||||
|
||||
Transaction fees
|
||||
----------------
|
||||
|
||||
You can charge extra fees to your customers for paying with Paypal;
|
||||
This to cover the transaction fees Paypal charges you. Once redirected to Paypal, your customer sees an extra applied to the order amount.
|
||||
|
||||
To activate this, go to the Configuration tab of Paypal configuration in
|
||||
Odoo and check *Add Extra Fees*.
|
||||
|
||||
.. image:: media/paypal10.png
|
||||
:align: center
|
||||
|
||||
You can refer to `Paypal Fees <https://www.paypal.com/webapps/mpp/paypal-fees>`__ to set up
|
||||
fees.
|
||||
|
||||
..note:: `Traders in the EU <https://europa.eu/youreurope/citizens/consumers/shopping/pricing-payments/index_en.htm>`__
|
||||
are not allowed to charge extra fees for paying with credit cards.
|
||||
|
||||
Go live!
|
||||
========
|
||||
|
||||
Your configuration is ready to roll. Make sure *Production* mode is
|
||||
on. Then publish the payment method by clicking the *Published* button right next to it.
|
||||
|
||||
.. image:: media/paypal11.png
|
||||
:align: center
|
||||
|
||||
.. image:: media/paypal12.png
|
||||
:align: Center
|
||||
|
||||
Paypal is now available in your payment form available in eCommerce,
|
||||
Sales and Invoicing apps. Customers are redirected to Paypal website
|
||||
when hitting *Pay Now*. They get back to a confirmation page in Odoo
|
||||
once the payment is processed.
|
||||
|
||||
.. image:: media/paypal13.png
|
||||
:align: center
|
||||
|
||||
Test environment
|
||||
================
|
||||
|
||||
You can test the entire payment flow in Odoo thanks to Paypal Sandbox accounts.
|
||||
|
||||
Log in to `Paypal Developer Site <https://developer.paypal.com/>`__ with your Paypal credentials.
|
||||
|
||||
This will create two sandbox accounts:
|
||||
|
||||
- A business account (to use as merchant, e.g. `pp.merch01-facilitator@example.com <mailto:pp.merch01-facilitator@example.com>`__).
|
||||
|
||||
- A default personal account (to use as shopper, e.g. `pp.merch01-buyer@example.com <mailto:pp.merch01-buyer@example.com>`__).
|
||||
|
||||
Log in to Paypal Sandbox with the merchant account and follow the same configuration instructions.
|
||||
Enter your sandbox credentials in Odoo and make sure Paypal is still
|
||||
set on *Test Environment*. Also, make sure the automatic invoicing
|
||||
is not activated in your eCommerce settings, to not generate invoices
|
||||
when a fictitious transaction is completed.
|
||||
|
||||
Run a test transaction from Odoo using the sandbox personal account.
|
||||
|
||||
See also
|
||||
|
||||
`How to manage orders paid with payment acquirers <https://www.odoo.com/documentation/user/12.0/ecommerce/shopper_experience/payment.html>`__
|
||||
|
||||
`How to manage orders paid with payment acquirers <https://www.odoo.com/documentation/user/12.0/ecommerce/shopper_experience/payment_acquirer.html>`__
|
||||
@@ -0,0 +1,38 @@
|
||||
=================================================
|
||||
How customers can access their customer account
|
||||
=================================================
|
||||
|
||||
It has never been so easy for your customers to access their
|
||||
customer account. Forget endless signup forms,
|
||||
Odoo makes it as easy as ABC.
|
||||
They are suggested to sign up (name, email, password) when the order
|
||||
is placed, and not before.
|
||||
Indeed, nothing is more annoying than going through a signup process
|
||||
before buying something.
|
||||
|
||||
Sign up
|
||||
=======
|
||||
|
||||
The invitation to sign up shows up when the customer wants to visualize
|
||||
the order from order confirmation email.
|
||||
|
||||
.. image:: ./media/portal_odoo_signup.png
|
||||
:align: center
|
||||
|
||||
Customer account
|
||||
================
|
||||
|
||||
Once logged in the customer will access the account by clicking *My Account*
|
||||
in the login dropdown menu.
|
||||
|
||||
.. image:: ./media/portal_link.png
|
||||
:align: center
|
||||
|
||||
THere they find all their history. The main address (billing) can also be modified.
|
||||
|
||||
.. image:: ./media/portal_menu.png
|
||||
:align: center
|
||||
|
||||
.. note::
|
||||
If the customer is set as a contact of a company in your address book,
|
||||
they will see all the documents whose the customer belongs to this company.
|
||||
@@ -0,0 +1,42 @@
|
||||
=======================================
|
||||
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!
|
||||
|
||||
|
||||
How to provide customers with payment instructions
|
||||
==================================================
|
||||
Put your payment instructions in the **Thanks Message** of your payment method.
|
||||
|
||||
.. image:: media/payment_instructions.png
|
||||
:align: center
|
||||
|
||||
They will appear to the customers when they place an order.
|
||||
|
||||
.. image:: media/payment_customer_instructions.png
|
||||
:align: center
|
||||
|
||||
|
||||
How to manage an order once you get paid
|
||||
========================================
|
||||
|
||||
Whenever a customer pays by wire transfer, the order stays in an
|
||||
intermediary stage **Quotation Sent** (i.e. unpaid order).
|
||||
When you get paid,
|
||||
you confirm the order manually to launch the delivery.
|
||||
|
||||
|
||||
How to create other manual payment methods
|
||||
==========================================
|
||||
|
||||
If you manage a B2B business, you can create other manually-processed
|
||||
payment methods like paying by check.
|
||||
To do so, just rename *Wire Transfer* or duplicate it.
|
||||
|
||||
.. image:: media/payment_check.png
|
||||
:align: center
|
||||