Card-to-card money transfer

Overview

Money transfer is a payment type which uses one request to initiate debiting funds from the sender's card and subsequently crediting these funds to the recipient's card. In the ECommPay payment platform, money transfers are supported for Mastercard and Visa cards, and they can be sent from one customer to another as well as between the cards of the same customer.

The payment workflow

In the payment platform, the following money transfer processing workflows are available: basic and partial. In case of the basic money transfer workflow, both the debiting and the crediting of funds are completed through the ECommPay payment platform, while the partial money transfer workflow implies either the debiting or the crediting of funds. The partial money transfer workflow is relevant when the merchant needs to process debiting the funds from the sender's card or crediting the funds to the recipient's card through an external payment services provider.

Basic and partial money transfer processing workflows are described below.

  1. You initiate basic money transfer workflow by sending a money_transfer request to the payment platform. Once the payment platform receives the request, it creates and then consecutively executes the following operations:
    • a sale operation which results in debiting the card of the sender. If at this stage the operation sale is declined, then crediting the recipient's card is declined as well.
    • a payout operation which results in crediting the card of the recipient. If at this stage the operation payout is declined, the payment platform automatically initiates a cancellation of the sale operation (i.e. a reversal operation).
  2. You initiate partial money transfer workflow by sending either a money_transfer/in request or money_transfer/out to the payment platform. According to the type of the request, one of the following operations is created:
    • a sale operation which results in debiting the card of the sender—for the money_transfer/in request;
    • a payout operation which results in crediting the card of the recipient—for the money_transfer/out request.

The relationship diagram for requests, payments, and operations below demonstrates that a single request for money transfer sent by a merchant results in two operations initiated in the payment platform. The operation which reverses the debiting of funds is initiated automatically by the payment platform.

Regardless of the workflow type, sending an additional request may be required if the 3-D Secure authentication of the customer is needed. For more detailed information on the 3-D Secure authentication, see 3-D Secure 2 and Customer authentication by using the 3‑D Secure 1.

Requesting additional information is not allowed for this payment type. This means that the platform does not send a callback to the web service in order to clarify any parameters, and that all necessary parameters should be included in the initial money transfer request. Therefore, when money transfers are sent in the countries which require Address Verification Service, an initial request should include an AvsInfo object which specifies the address kept on file as current by the issuer for the sender of the money transfer (postal code and street address).

Figure: State diagram for money transfer

The rest of this section describes all possible statuses of a money transfer and operations related to it. For more detailed information on money transfer processing, see Card-to-card money transfer.

Payment statuses

The following table describes the statuses of a money transfer.

error Error occurred when request processing. Payment is not performed. Final status. The request can be resent with the same payment identifier.
processing Payment is being processed. Intermediate status
awaiting 3ds result Payment processing is suspended until the web service submits a 3ds_result request with the authentication result. If the payment platform does not receive this request within 30 minutes, then the payment status is set to decline. Intermediate status
decline Payment has not been completed because debiting of funds was declined. Final status
reversed Payment has not been completed because crediting of funds was declined. Final status
success Payment has been completed. Final status

Statuses of the sale operation

The following table describes the statuses of the sale operation.

processing Operation is being processed. Intermediate status
awaiting 3ds result Operation processing is suspended until the web service submits a 3ds_result request with the authentication result. If the payment platform does not receive this request within 30 minutes, then the operation status is set to decline. Intermediate status
decline Operation has not been completed. Final status
success Operation has been completed. Final status

Statuses of the payout operation

The following table describes the statuses of the payout operation.

processing Operation is being processed. Intermediate status
decline Operation has not been completed. Final status
success Operation has been completed. Final status

Statuses of the reversal operation

The following table describes the statuses of the reversal operation.

processing Operation is being processed. Intermediate status
success Operation has been completed. Final status

Related links