-
Notifications
You must be signed in to change notification settings - Fork 10.6k
[IMP] payment providers: Wire Transfer #4445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
65 changes: 36 additions & 29 deletions
65
content/applications/finance/payment_acquirers/wire_transfer.rst
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,40 +1,47 @@ | ||
| =================================== | ||
| How to get paid with wire transfers | ||
| =================================== | ||
| ============== | ||
| 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! | ||
| The **Wire transfer** payment method allows you to provide payment instructions to your customers, | ||
| such as the bank details and communication. They are displayed: | ||
|
|
||
| How to provide customers with payment instructions | ||
| ================================================== | ||
| - at the end of the checkout process, once the customer has selected :guilabel:`Wire transfer` as a | ||
| payment method and clicked the :guilabel:`Pay now` button: | ||
|
|
||
| Put your payment instructions in the **Thanks Message** of your payment method. | ||
| .. image:: wire_transfer/payment_instructions_checkout.png | ||
| :alt: Payment instructions at checkout | ||
|
|
||
| .. image:: wire_transfer/payment_instructions.png | ||
| :align: center | ||
| - on the customer portal: | ||
|
|
||
| .. image:: wire_transfer/payment_instructions_portal.png | ||
| :alt: Payment instructions on the customer portal | ||
|
|
||
| .. note:: | ||
| - While this method is very accessible and requires minimal setup, it is very inefficient | ||
| process-wise. We recommend setting up a :doc:`payment acquirer <../payment_acquirers>` instead. | ||
| - Online orders remain in the :guilabel:`Quotation sent` (i.e., unpaid order) stage until you | ||
| receive the payment and :guilabel:`Confirm` the order. | ||
|
|
||
| They will appear to the customers when they place an order. | ||
| .. tip:: | ||
| **Wire transfer** can be used as a template for other payment methods that are processed | ||
| manually, such as checks, by renaming or duplicating it. | ||
|
|
||
| .. image:: wire_transfer/payment_customer_instructions.png | ||
| :align: center | ||
| Configuration | ||
| ============= | ||
|
|
||
| How to manage an order once you get paid | ||
| ======================================== | ||
| **Wire Transfer** is installed and enabled by default. | ||
auva-odoo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| 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. | ||
| To configure it, go to :menuselection:`Accounting / Website --> Configuration --> | ||
| Payment Acquirers`, and open the :guilabel:`Wire Transfer` card. Then, select the | ||
| :guilabel:`Communication` to be used in the :guilabel:`Configuration` tab: | ||
|
|
||
| How to create other manual payment methods | ||
| ========================================== | ||
| - :guilabel:`Based on Document Reference`: sales order or invoice number | ||
| - :guilabel:`Based on Customer ID`: customer identifier | ||
|
|
||
| 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. | ||
| Define the payment instructions in the :guilabel:`Messages` tab: | ||
|
|
||
| .. image:: wire_transfer/payment_instructions.png | ||
| :alt: Define payment instructions | ||
|
|
||
| .. image:: wire_transfer/payment_check.png | ||
| :align: center | ||
| .. seealso:: | ||
| :doc:`../accounting/getting_started/cheat_sheet` | ||
Binary file removed
BIN
-22.4 KB
content/applications/finance/payment_acquirers/wire_transfer/payment_check.png
Binary file not shown.
Binary file removed
BIN
-37 KB
...tions/finance/payment_acquirers/wire_transfer/payment_customer_instructions.png
Binary file not shown.
Binary file modified
BIN
-25.5 KB
(19%)
...t/applications/finance/payment_acquirers/wire_transfer/payment_instructions.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+10.5 KB
...tions/finance/payment_acquirers/wire_transfer/payment_instructions_checkout.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+36.4 KB
...cations/finance/payment_acquirers/wire_transfer/payment_instructions_portal.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.