Requests, payments, operations

The ecommpay payment platform is used to process payment, acting as an intermediary between the merchant and the customer. Payment created in the payment platform is a set of tasks to transfer funds between them. In the ecommpay payment platform there are following payment types:

• purchase—one-time transfer of funds from customer to merchant performed in one step or two steps.
• recurring—repeated transfer of funds from customer to merchant on demand or auto performed.
• invoice—payment link purchase, in one step or two steps.
• payout—transfer of funds from merchant to customer.
• account verification—checking a customer card validity that can include transferring of zero amount funds or holding of a specified amount on the customer card account and subsequent cancellation of this holding.

There are several ways to initialise a payment. You can send an HTTP request by using the Gate API or the Payment Page API or use the Dashboard interface. If a request to perform payment is successfully accepted for processing, in the payment platform the payment object and the first (or the only one) operation object associated with this payment are created.

Figure: The relationship diagram for requests, payments, and operations

When the payment takes more that one operations, normally merchant needs to send the request for initiating to each subsequent operation. However, in some cases, the payment platform automatically initiates the subsequent operation, for instance the recurring operation included in the automatic recurring payment.

The following sections covers the information about each payment type.