.. _echeck_integration:

eCheck Sale
###########

.. toctree::
   :maxdepth: 3

.. contents::
   :local:

.. role:: ex

.. role:: code

Introduction
------------

| Payneteasy allows Connecting Party to accept electronic check payments for goods and services purchased via e-commerce websites. An electronic check works much like a regular check, only instead of using a paper check to provide their bank account, routing number and payment authorization, the Payer provides Connecting Party with the necessary payment information through other methods, allowing the Connecting Party to process the information electronically.
|
| See terms definitions in :ref:`Glossary<glossary>`.

eCheck Flow
-----------

.. uml::
  :align: center

  skinparam roundcorner 20
  skinparam sequenceArrowThickness 1
  skinparam maxmessagesize 1200
  skinparam sequenceParticipant underline
  actor Payer
  participant "Connecting Party" as A
  participant Payneteasy as B
  autonumber
  Payer -> A: Checkout
  activate A
  A -> B: /api/v2/sale-echeck/
  activate B
  B --> A: Order ID
  B -> B: Process\nSale-eCheck
  group Get Final Status
  == Receive Connecting Party Callback ==
  A <- B: Callback with Final Status
  A --> B: HTTP 200
  deactivate B
  == Order Status Request ==
  A -> B: Get Status by Order ID
  activate B
  B --> A: Final Status
  deactivate B
  end
  A --> Payer: Show result
  deactivate Payer
  deactivate A


| (2) To implement sale-eCheck request see :ref:`/api/v2/sale-echeck/</api/v2/sale-echeck/>`.
| (5) To implement callback with final status handling see :ref:`Connecting Party Callback<merchant_callbacks>`.
| (7) To implement order status request see :ref:`/api/v2/status/</api/v2/status/>`. Status should be requested multiple times with 3-5 seconds interval until final status will be received in response.