Payments by card-to-card money transfer via partner

Overview

This payment method allows customers to perform purchases by card-to-card money transfer from the customer card to the card specified by the partner. Most often customers perform such transfers via the online-banking application, the card number must be entered correctly according to instruction provided to customers on the partner side. Purchases through this method can be performed by using Payment Page and Gate.

General information

Payment method type P2P
Countries and regions RU
Payment currencies RUB
Currency conversion on the ECommPay side
Purchases +
Payouts +
Stored credentials payments
Full refunds
Partial refunds
Chargebacks
Special considerations
Obtaining access to the payment method and access fee refer to your ECommPay key account manager

Interaction diagram

Payment processing by using the payment method requires merchant's web service, one of ECommPay interfaces, and the ECommPay payment platform, as well as partner technical facilities.



Operations support

  Interfaces Amounts, RUB
Payment Page CMS Plug-ins Gate Dashboard minimum maximum
Purchases + + * *
Payouts + 10.00 150,000.00

* Amount limits and payment processing times depend on issuer banks.

Processing scenarios

To perform a purchase operation, you need to redirect customer to the partner service, while to perform a payout, you need to notify customer via merchant's web service.

Figure: Purchase by using Payment Page



Figure: Purchase by using Gate



Figure: Payout by using Gate



The sections that follow provide detailed information about what you need to perform payments and how you can analyse the information on payments and operations.

Purchases by using Payment Page

General information

In the partner method, when processing a purchase by using Payment Page, the merchant web service should send a request with all the required parameters and signature to the ECommPay URL and get the callback with the payment result from the payment platform. When opening Payment Page, you can have Payment Page opened with the method selected. For more information about preselecting payment methods, see in Preselecting payment method. The full sequence and particularities of the purchase process are provided below.



Figure: Purchase by using Payment Page

  1. A customer initiates a purchase on the merchant's web service.
  2. The web service sends the request for Payment Page opening to the specified ECommPay URL.
  3. The request for opening is redirected to the payment platform.
  4. The payment platform performs the initial request processing that involves validation of the required parameters and signature.
  5. Requested Payment Page is generated into the ECommPay payment platform as specified in the project settings and the request parameters.
  6. Payment Page is displayed to the customer.
  7. The customer selects the payment method.
  8. The payment platform receives the purchase request for payment processing from Payment Page.
  9. The payment platform performs the internal purchase request processing.
  10. The payment platform sends the customer redirection data to Payment Page.
  11. The customer is redirected to the partner website with the payment instructions.
  12. The customer acts according to the payment instructions and uses the bank application or the bank website to specify the payment amount and transfer the funds.
  13. The payment is processed on the partner side.
  14. The customer is redirected to Payment Page.
  15. The partner service sends the result notification to the payment platform.
  16. The payment platform sends a callback with the payment result to the web service.
  17. The payment platform sends the result to Payment Page.
  18. A page with the payment result information is displayed to the customer on Payment Page.

The sections that follow discuss in more details the request format and the Payment Page parameters to use in the payment method and provide the information on the format of callbacks with payment results. For the general information on how to use the API, see Payment Page API Description.

Request format

There are several things you need to consider when using the method:

  1. You must provide values for the basic minimum of parameters. Listed below are the parameters that are mandatory for any payment method:
    • project_id—the project ID obtained from ECommPay
    • payment_id—payment ID unique within the project
    • payment_currency*—payment currency in ISO-4217 alpha-3 format
    • payment_amount*—payment amount in minor units
    Note: * When preselecting the payment method the parameters payment_currency and payment_amount are not mandatory, as the customer specifies the purchase amount when transferring funds by using the bank application or the bank website.
  2. There is one more mandatory parameter—customer_id. In the customer_id parameter, you must specify the ID of the customer within your project.
  3. If you need to have Payment Page displayed with the method selected, set the force_payment_method parameter to card-p2p.
  4. If required, you can also add any other additional parameters Payment Page supports.
  5. After you specify all the parameters you need, you must create the signature for the request. For instructions on how to sign a payment request, see Signature generation and verification.

Thus, a correct payment request in the method must include project, customer and payment IDs, ID of the payment method and signature, as shown in the following example:

    { payment_id: 'X03936', 
      force_payment_method: 'card-p2p',
      customer_id: '001',
      project_id: 12, 
      signature: "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8...VUkDJrOcZzUCwX6R\/ekpZhkIQg=="
    }

For information about all parameters available in the method , see Payment Page invocation parameters.

Callback format

The method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks.

The following is the example of a callback with an information about successful 100.00 RUB purchase made by the user45 customer in the 239 project. The purchase amount in the callback is the amount that the customer specifies when transferring funds by using the bank application or the bank website.

Figure: Example of a successful purchase callback

{
        "customer": {
            "id": "user45"
        },
        "project_id": 1625,
        "payment": {
            "id": "ID_748492",
            "type": "purchase",
            "status": "success",
            "date": "2020-04-22T14:48:20+0000",
            "method": "card-p2p",
            "sum": {
                "amount": 10000,
                "currency": "RUB"
            },
            "description": "ID_748492"
        },
        "operation": {
            "id": 54851000040741,
            "type": "sale",
            "status": "success",
            "date": "2020-04-22T14:48:20+0000",
            "created_date": "2020-04-22T14:45:37+0000",
            "request_id": "7efb61c83c91645a05d1cbf...c9924f4ff19a36596a-00054852",
            "sum_initial": {
                "amount": 10000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "RUB"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 2721,
                "payment_id": "",
                "auth_code": ""
            }
        },
        "signature": "A9w013/aPMSTIFkleQ4GaUcawu...kTav8yNuSChjPdHbgC5OimQ=="
    }

The following is the example of a callback for a declined purchase.

Figure: Example of a declined purchase callback

{
        "customer": {
            "id": "2"
        },
        "project_id": 1625,
        "payment": {
            "id": "ID_748493",
            "type": "purchase",
            "status": "decline",
            "date": "2020-04-22T15:48:20+0000",
            "method": "card-p2p",
            "sum": {
                "amount": 10000,
                "currency": "RUB"
            },
            "description": "ID_748492"
        },
        "operation": {
            "id": 54851000040741,
            "type": "sale",
            "status": "decline",
            "date": "2020-04-22T15:48:20+0000",
            "created_date": "2020-04-22T14:45:37+0000",
            "request_id": "7efb61c83c91645a05d1cbf...c9924f4ff19a36596a-00054853",
            "sum_initial": {
                "amount": 10000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "RUB"
            },
            "code": "20000",
            "message": "General decline",
            "provider": {
                "id": 2721,
                "payment_id": "",
                "auth_code": ""
            }
        },
        "signature": "A9w013/aPMSTIFkleQ4GaUcawu...kTav8yNuSChjPdHbgC5UnmQ=="
    }

Related topics

The following topics might be useful when implementing payments by using Payment Page:

Purchases by using Gate

General information

In the method, when processing a purchase by using Gate, the merchant web service is required to do the following:

  1. Send a request with all the required parameters and signature to the ECommPay URL.
  2. Perform the redirection of a customer to the partner service.
  3. Get the callback with the payment result from the payment platform.

The following diagram provides the detailed picture of the payment processing procedure.



Figure: Purchase by using Gate

  1. A customer initiates a purchase through partner on the merchant's web service side.
  2. The web service sends the request for processing the purchase by using Gate to the specified ECommPay URL.
  3. The payment platform receives the request for processing the purchase from Gate.
  4. The payment platform performs the initial request processing that includes validation of the required parameters and signature.
  5. The payment platform sends the response with request receipt confirmation and correctness check result to the web service. For more information, see Response format.
  6. The payment platform performs the internal payment request processing.
  7. The payment platform sends the callback with the redirection data in the redirect_data object to the web service.
  8. The customer is redirected to the partner website with the payment instructions.
  9. The customer acts according to the payment instructions and uses the bank application or the bank website to specify the payment amount and transfer the funds.
  10. The payment is processed on the partner side.
  11. The customer is redirected to the merchant's web service.
  12. The partner service sends the payment result notification to the payment platform.
  13. The payment platform sends a callback to the web service.
  14. The customer receives the payment result from the web service.

The sections that follow discuss in more details the request format and the Gate parameters to use in the payment method and provide the information on the format of callbacks with purchase results.

Request format

There are several things you must consider when using purchase requests in the method:

  1. You send purchase requests by sending the /v2/payment/card-p2p/sale request by using the POST HTTP method .
  2. The following objects and parameters must be specified in any request:
    • Object general—general request identification information:
      • project_id—the project ID obtained from ECommPay
      • payment_id—payment ID unique within the project
      • signature—signature created after you specify all the required parameters. For more information about signature generation, see Signature generation and verification.
    • Object customer—customer information:
      • id—identifier on the web service side
      • ip_address—customer IP address
    • Object return_url—contains the URLs to which customer is redirected while or after payment processing:
      • return—URL to return customer to the web service during any step before the payment is completed with a click of the return button.
  3. If required, you can also add any other additional parameters Gate supports.

Thus, a correct payment request in the method must include project and payment IDs, signature, customer information and URL for redirection as shown in the following example:

Figure: Example of a purchase request

{ 
   "general": { 
      "project_id": 874,
      "payment_id": "561719496",
      "signature": "fCkXYCxiTjiN9AkFvEZCp...crW0r3wcXQggExZHbeXH/VPAMbywQ=="
   },
   "customer": { 
      "id": "245",
      "ip_address": "1.2.3.4"
   },
    "return_url": {
      "return": "http://example.com/return"
   }  
}

Formats of the customer redirection data

To redirect a customer from the web service to the partner site, you must receive a callback from the payment platform containing the URL for redirection in the redirect_data.url parameter and data to be sent in the request body in the redirect_data.body parameter, and use these parameters when opening the HTML page using the method specified in the redirect_data.method parameter.

The following is the callback fragment containing the redirection data.

"redirect_data": {
    "body": {},
    "method": "GET",
    "url": "https://api.p2pbank.online/example_test"
  }

Callback format

The method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks.

The following is the example of a callback with an information about successful 100.00 RUB purchase made by the user45 customer in the 239 project. The purchase amount in the callback is the amount that the customer specifies when transferring funds by using the bank application.

Figure: Example of a successful purchase callback

{
        "customer": {
            "id": "user45"
        },
        "project_id": 1625,
        "payment": {
            "id": "ID_748492",
            "type": "purchase",
            "status": "success",
            "date": "2020-04-22T14:48:20+0000",
            "method": "card-p2p",
            "sum": {
                "amount": 10000,
                "currency": "RUB"
            },
            "description": "ID_748492"
        },
        "operation": {
            "id": 54851000040741,
            "type": "sale",
            "status": "success",
            "date": "2020-04-22T14:48:20+0000",
            "created_date": "2020-04-22T14:45:37+0000",
            "request_id": "7efb61c83c91645a05d1cbf...c9924f4ff19a36596a-00054852",
            "sum_initial": {
                "amount": 10000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "RUB"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 2721,
                "payment_id": "",
                "auth_code": ""
            }
        },
        "signature": "A9w013/aPMSTIFkleQ4GaUcawu...kTav8yNuSChjPdHbgC5OimQ=="
    }

The following is the example of a callback for a declined purchase.

Figure: Example of a declined purchase callback

{
        "customer": {
            "id": "2"
        },
        "project_id": 1625,
        "payment": {
            "id": "ID_748493",
            "type": "purchase",
            "status": "decline",
            "date": "2020-04-22T15:48:20+0000",
            "method": "card-p2p",
            "sum": {
                "amount": 10000,
                "currency": "RUB"
            },
            "description": "ID_748492"
        },
        "operation": {
            "id": 54851000040741,
            "type": "sale",
            "status": "decline",
            "date": "2020-04-22T15:48:20+0000",
            "created_date": "2020-04-22T14:45:37+0000",
            "request_id": "7efb61c83c91645a05d1cbf...c9924f4ff19a36596a-00054853",
            "sum_initial": {
                "amount": 10000,
                "currency": "RUB"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "RUB"
            },
            "code": "20000",
            "message": "General decline",
            "provider": {
                "id": 2721,
                "payment_id": "",
                "auth_code": ""
            }
        },
        "signature": "A9w013/aPMSTIFkleQ4GaUcawu...kTav8yNuSChjPdHbgC5UnmQ=="
    }

Related topics

The following topics might be useful when implementing payments through Gate:

Payouts by using Gate

General information

To perform a payout through the method, merchant's web service sends a request with all the required parameters and signature to ECommPay URL, and receives a callback with the payment result. The full sequence of the payout process is provided below.



Figure: Payout by using Gate

  1. A customer orders a payout through the merchant web service.
  2. Merchant web service sends the request for the payout processing by using Gate to the appropriate ECommPay URL.
  3. Gate redirects the request to the ECommPay payment platform.
  4. The payment platform performs all the necessary checks and processes the request.
  5. The reply with the request processing results is sent to the merchant's web service. For more information, see Response format.
  6. The payment platform redirects the payout request to the partner service.
  7. The payout is processed on the partner side.
  8. Partner sends the result notification to the payment platform.
  9. The payment platform sends a callback with the payment result to the web service.
  10. The customer receives the notification about the payout result from the web service.
Note: The payout processing is similar to the processing of payout to payment card. To perform a payout, send payout request by sending the /v2/payment/card/payout request by using HTTP method POST.

Information on the format of requests and parameters for initiating payouts by using Gate, as well as on the format of callbacks with the payout results is given in the Payout section; for general information on working with the API, see the section API Description.

Related topics

The following topics might be useful when implementing payments through Gate:

Analysis of payments results

As with other payment methods ECommPay offers, when using the partner method, you have several options to analyse the information about payments and operations performed by using the method—alone or in conjunction with other methods.

You can load and analyse all the necessary information in Dashboard, for instance you can use the analytic panels on the Analytics tab to this end.

Also, you can export the information for further analysis by using third party analytical tools. The following options are available:

  • Dashboard allows you to download reports in CSV and XLS formats—by using the tools on the Payments tab. You can perform export as a one-time download to your local computer or have payment data regularly exported and delivered to email addresses you specify.
  • Data API allows you to have payment information exported in JSON format and delivered to a URL you specify. The payment information is exported by using the /operations/get queries.

If you have any further questions regarding payment data analysis, contact ECommPay technical support.