Files
documentation/content/applications/sales/point_of_sale/payment/vantiv.rst
T
Antoine Vandevenne (anv) 8722ea902e [MOV] content/*: move resource files into their related page's directory
Since odoo/documentation#903, the guideline for the location of new
resource (images, downloadable files, RST includes...) files is to place
those inside the directory of the RST page that references them.

For example, if `doc1.rst` has a reference to `image.png` and to
`download.zip`, the file structure should look like this:

├── parent_doc/
│     └── doc1/
│     │     └── image.png
│     │     └── download.zip
│     └── doc1.rst
│     └── doc2.rst
├── parent_doc.rst

Before this commit, most of the resource files were still located inside
'media' directories holding all the resource files referenced by RST
pages located at the same level as these directories. In the example
above, a single 'media' directory would hold all the resource files
referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from
figuring out easily which resource file was referenced by which RST page
and, thus, lead to unused resource files piling up in the repository. It
also made it more complicated to define codeowners regex rules because a
team could not simply be assigned to `/some_page.*` but needed to be
assigned to both `/some_page\.rst` and to the location of 'media'.

In order to help new content writers figure out the guideline when
taking examples from other RST pages, this commit retroactively applies
the guideline to existing resource files and 'media' directories. The
left-over resource files that are not referenced by any RST page are
removed.

task-2497965

Part-of: odoo/documentation#2068
2022-05-20 14:18:54 +02:00

46 lines
1.4 KiB
ReStructuredText
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
=============================================
Connect a Vantiv Payment Terminal to your PoS
=============================================
Connecting a Vantiv payment terminal allows you to offer a fluid payment
flow to your customers and ease the work of your cashiers.
.. note::
Please note MercuryPay only operates with US and Canadian banks, making
this procedure only suitable for North American businesses.
Configuration
=============
Configure the Payment Method
----------------------------
First, go in the general settings of the POS app, and activate the
Vantiv setting.
.. image:: vantiv/vantiv_01.png
:align: center
Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the
payments section and access your payment methods. Create a new payment
method for Vantiv, select the payment terminal option Vantiv, and create
new Vantiv credentials.
.. image:: vantiv/vantiv_02.png
:align: center
To create new Vantiv credentials, fill in your merchant ID and password,
then save. Make sure the credentials you just created are selected, then
save the payment method.
.. image:: vantiv/vantiv_03.png
:align: center
Pay with a Payment Terminal
===========================
In your PoS interface, at the moment of the payment, select your Vantiv
payment method and… thats all.
.. image:: vantiv/vantiv_04.png
:align: center