EPS

Overview

EPS is a payment method that allows customers to perform payments by using bank transfer of the Austrian banks. Purchases are performed by using Payment Page and Gate.

General information

Payment method type bank payments
Payment instruments bank accounts
Countries and regions AT
Payment currencies EUR
Currency conversion On ecommpay side
Purchases +
Payouts –
Stored credentials payments –
Full refunds –
Partial refunds –
Chargebacks –
Notes –
Onboarding and access fee Refer to your ecommpay key account manager

Interaction diagram

Payment processing by using the EPS payment method requires merchant's web service, one of ecommpay interfaces, and the ecommpay payment platform, as well as EPS service which is supported interactions with banks.



Operations support

  Interfaces Amounts, EUR * Times **
Payment Page CMS Plug-ins Gate Dashboard minimum maximum Basic Threshold
Purchases + – + – 1.00 10,000.00 within 10 minutes up to 48 hours

* Refer to the ecommpay key account manager for more information on amount limits.

** The basic and threshold times are defined as follows:
  • The basic time is the average estimated time between the moment a payment is initiated in the payment platform to the moment the payment result is sent to the initiator. The basic time evaluation is made on the assumption of normal operation of all technical facilities and communication channels and typical customer behaviour (if any input from customer is required). Use the basic time to estimate when to react to the absence of payment result notifications or when to check payment status.
  • The threshold time is the maximum possible time between the moment a payment is initiated in the payment platform to the moment the initiator receives the callback with the payment result. A payment is automatically declined, if its waiting time exceeds the threshold time. For individual setting of the threshold time limit, contact ecommpay technical support.

Processing scenarios

To perform a purchase operation, you need to redirect a customer to the EPS or bank service.

Figure: Purchase by using Payment Page



Figure: Purchase 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.

Purchase by using Payment Page

General information

In the EPS method, to perform 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 EPS method selected. For more information about preselecting payment methods, see in Preselecting payment methods.

The full sequence and particularities of the purchase process are provided below.



Figure: Purchase sequence 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 EPS method.
  8. The payment platform receives the purchase request for payment processing.
  9. The payment platform performs the internal purchase request processing and sends it to the EPS service.
  10. The purchase request is processed on the EPS service side.
  11. The service generates the data for redirecting the customer to its payment form and sends it to the payment platform.
  12. The payment platform sends the customer redirection data to Payment Page.
  13. The customer is redirected to the EPS service.
  14. The customer completes all the payment steps required.
  15. The payment is processed on EPS side.
  16. The result is displayed to the customer on the service.
  17. The customer is redirected to Payment Page.
  18. EPS sends the result notification to the payment platform.
  19. The payment platform sends a callback with the payment result to the web service.
  20. The payment platform sends the result to Payment Page.
  21. 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 EPS 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 requesting a payment through the EPS method:

  1. You must provide values for the basic minimum of parameters. Listed below are the parameters that are mandatory for any payment method:
    • customer_id—the unique ID of the customer within your project
    • 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
  2. The currency of a payment can only be EUR.
  3. There are more mandatory parameters customer_first_name, customer_last_name, customer_email—first and last names, email of the customer within the project. If the parameters are not passed in the request for Payment Page opening, they are requested from customer on additional page.
  4. If you need to have payment form displayed with the EPS method selected, set the force_payment_method parameter to eps.
  5. If required, you can also add any other additional parameters Payment Page supports.
  6. 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 EPS method must include project, customer and payment IDs, the currency and the amount of the payment, and customer data, as shown in the following example:

EPayWidget.run(
    { project_id: 0, 
      payment_id: 'X03936',
      payment_amount: 1000, 
      payment_currency: 'EUR', 
      customer_id: '123',
      customer_first_name: 'John',
      customer_last_name: 'Johnson',
      customer_email: 'John@mail.com',
      signature: "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y1Y4HASCQ9vySODJrOcZzUCwX6R\/ekpZhkIQg=="
    }
)

For information about all parameters available in the EPS method, see Parameters for opening payment form.

Callback format

The EPS 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 10.00 EUR purchase from the customer in the 238 project.

Figure: Example of a successful purchase callback

{
{
        "project_id": 238,
        "payment": {
            "id": "TEST_1560760354708",
            "type": "purchase",
            "status": "success",
            "date": "2019-06-17T08:56:47+0000",
            "method": "eps",
            "sum": {
                "amount": 1000,
                "currency": "EUR"
            },
            "description": ""
        },
        "operation": {
            "id": 29891000002914,
            "type": "sale",
            "status": "success",
            "date": "2019-06-17T08:56:47+0000",
            "created_date": "2019-06-17T08:50:34+0000",
            "request_id": "0d6aabd20c7925f1719b7cb63f728b32a3450cf0",
            "sum_initial": {
                "amount": 1000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 1000,
                "currency": "EUR"
            },
            "provider": {
                "id": 1208,
                "payment_id": "148907",
                "date": "2019-06-17T08:56:46+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "V0zYWk7OzwfcMBAJJxArOuQoQfNv92z0wBJeQIHwj75hpkuXFNqHjYGMdfhycMw=="
    }
}

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

Figure: Example of a declined purchase callback

{
{
        "project_id": 238,
        "payment": {
            "id": "TEST_156162712312",
            "type": "purchase",
            "status": "decline",
            "date": "2019-06-27T12:53:58+0000",
            "method": "eps",
            "sum": {
                "amount": 500,
                "currency": "USD"
            },
            "description": "TEST_1561627597648"
        },
        "customer": {
            "id": "1"
        },
        "operation": {
            "id": 1590021,
            "type": "sale",
            "status": "decline",
            "date": "2019-06-27T12:53:58+0000",
            "created_date": "2019-06-27T12:49:41+0000",
            "request_id": "935dc4ba8b35ca5046",
            "sum_initial": {
                "amount": 500,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 440,
                "currency": "EUR"
            },
            "provider": {
                "id": 1239,
                "payment_id": "922806",
                "date": "2019-06-27T12:53:57+0000",
                "auth_code": ""
            },
            "code": "20000",
            "message": "General decline"
        },
        "signature": "S4qhcifHHzZgnOwRC0GSsEfoPl9zyGnNp7g=="
    }
}

Related topics

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

Purchase by using Gate

General information

In the EPS methods, 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 EPS 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 EPS 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 and redirects the request to the EPS service.
  7. The request is processed on the EPS side.
  8. The EPS service sends the data for redirecting the customer to the EPS service to the payment platform.
  9. The payment platform sends the callback with the redirection data in the redirect_data object to the web service.
  10. The customer is redirected from the web service to the EPS service.
  11. The customer completes all the payment steps required.
  12. The payment is processed on the EPS side.
  13. The result is displayed to the customer.
  14. The customer is redirected to the merchant's web service.
  15. The EPS service sends the payment result notification to the payment platform.
  16. The payment platform sends a callback to the web service.
  17. The customer receives the payment result on the web service.

The sections that follow discuss in more details the request format and the Gate parameters to use in the EPS 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 EPS method:
  1. You perform refunds by sending the /v2/payment/bank-transfer/eps/sale request by using POST (HTTP) method. This is a bank transferring request group: /v2/payment/bank-transfer/{payment_method}/sale
  2. The following objects and parameters must be specified in any request:
    • Object general—general purchase information:
      • project_id—project identifier
      • payment_id—unique purchase identifier
      • 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—the unique ID of the customer within your project
      • first_name—first name
      • last_name—last name
      • email—email address
      • ip_address—customer IP address
    • Object payment—purchase information:
      • amount—purchase amount
      • currency—payout currency in the ISO-4217 alpha-3 format.
    • return_url—URL for customer returning from the bank site:
      • return—site URL for returning
  3. The currency of a payment can only be EUR.
  4. If required, you can also add any other additional parameters Gate supports.

Thus, a correct payment request in the EPS method must include project, customer and payment IDs, customer data, currency and amount of the purchase, as shown in the following example:

Figure: Example of a purchase request

{
    "general": {
        "project_id": 2990,
        "payment_id": "payment_id",
        "signature": "PJkV8ej\/UG0Di8NN5e7cV+VHq3LwY3T\/pOMeSaRfBaNIipTv+AWoXW\/9MTO8yJA=="
    },
    "customer": {
      "id": "123",
      "ip_address": "1.1.1.1",
      "email": "Johnson@mail.com",
      "first_name": "John",
      "last_name": "Johnson"
    },
    "payment": {
      "amount": 1000,
      "currency": "EUR"
    },
    "return_url": {
      "return": "http://merchantsite.com"
    }
}

Formats of the customer redirection data

To redirect a customer from the web service to the EPS 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://example.com/en/payments/pay/0a0ffa98-98da-11eed6528a4861c"
                }

Callback format

The EPS 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 10.00 EUR purchase from the customer in the 238 project.

Figure: Example of a successful purchase callback

{
{
        "project_id": 238,
        "payment": {
            "id": "TEST_1560760354708",
            "type": "purchase",
            "status": "success",
            "date": "2019-06-17T08:56:47+0000",
            "method": "eps",
            "sum": {
                "amount": 1000,
                "currency": "EUR"
            },
            "description": ""
        },
        "operation": {
            "id": 29891000002914,
            "type": "sale",
            "status": "success",
            "date": "2019-06-17T08:56:47+0000",
            "created_date": "2019-06-17T08:50:34+0000",
            "request_id": "719b7cb63f728b32a3450cf0",
            "sum_initial": {
                "amount": 1000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 1000,
                "currency": "EUR"
            },
            "provider": {
                "id": 1208,
                "payment_id": "148907",
                "date": "2019-06-17T08:56:46+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "V0zYWk7OzwfcMBAJJxArOuQoQfNv92z0wBJeQIHwj75huXFNqHjYGMdfhycMw=="
    }
}

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

Figure: Example of a declined purchase callback

{
{
        "project_id": 238,
        "payment": {
            "id": "TEST_156162712312",
            "type": "purchase",
            "status": "decline",
            "date": "2019-06-27T12:53:58+0000",
            "method": "eps",
            "sum": {
                "amount": 500,
                "currency": "USD"
            },
            "description": "TEST_1561627597648"
        },
        "customer": {
            "id": "1"
        },
        "operation": {
            "id": 1590021,
            "type": "sale",
            "status": "decline",
            "date": "2019-06-27T12:53:58+0000",
            "created_date": "2019-06-27T12:49:41+0000",
            "request_id": "935dc4ba8b35ca5046",
            "sum_initial": {
                "amount": 500,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 440,
                "currency": "EUR"
            },
            "provider": {
                "id": 1239,
                "payment_id": "922806",
                "date": "2019-06-27T12:53:57+0000",
                "auth_code": ""
            },
            "code": "20000",
            "message": "General decline"
        },
        "signature": "S4qhcifHHzZgnOwRC0GSsEfoPl9zyGnNp7g=="
    }
}

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 EPS 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.