Skrill Wallet

Overview

Skrill Wallet is the electronic payment service that allows you to receive payments from customers, perform payments to customers by means of e-wallets. Purchases are performed by using Payment Page and Gate, COF payments, payouts and refunds—by using Gate.

General information

Payment method type Payments by using e-wallets
Countries and regions All
Payment currencies AUD, CAD, CHF, DKK, EUR, GBP, HUF, NOK, PLN, RON, SEK, USD *
Currency conversion
Purchases +
Payouts +
Stored credentials payments +
Full refunds +
Partial refunds +
Chargebacks
Notes
Onboarding and access fee Refer to your ECommPay key account manager ECommPay

* Specify the exact information with the ECommPay key account manager.

Note:

Two technical implementations are currently supported for working with the Skrill Wallet method: the new one described in this section and the old one described in the section Skrill Wallet (legacy).

Details about the difference between these implementations and how to switch from the old implementation to the new one should be clarified with the ECommPay key account manager.

Interaction diagram

Payment processing through the Skrill Wallet payment method requires merchant's web service, one of the interfaces and the payment platform of ECommPay, as well as Skrill Wallet technical facilities.



Operations support

  Interfaces Amounts *
Payment Page Mobile SDKs CMS Plug-ins Gate Dashboard (Old Dashboard) minimum maximum
Purchases + + + 0.50 EUR (or equivalent) 8,000.00 EUR (or equivalent)
COF payments +
Payouts + 10.00 USD (or equivalent) 10,000.00 USD (or equivalent)
Full refunds +
Partial refunds +

* Specify the exact information with the ECommPay key account manager.

Processing scenarios

In the Skrill Wallet method, to perform a purchase operation, you need to redirect a customer to the Skrill Wallet service, while a payout and a refund are performed with the notification of a customer via web service.

Figure: Purchase by using Payment Page procedure diagram



Figure: Purchase by using Gate procedure diagram



Figure: Refund by using Gate procedure diagram



Figure: Payout by using Gate procedure diagram



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 Skrill Wallet 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 Skrill Wallet 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 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 the Skrill Wallet 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 and sends it to the Skrill Wallet service.
  10. The purchase request is processed on the Skrill Wallet service side.
  11. The Skrill Wallet service generates the data for redirecting the customer to its website 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 Skrill Wallet website.
  14. The customer completes all the payment steps required.
  15. The payment is processed on the Skrill Wallet side.
  16. The result is displayed to the customer on the Skrill Wallet website.
  17. The customer is redirected to Payment Page.
  18. The Skrill Wallet service 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 Skrill Wallet 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 Skrill Wallet 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
    • customer_id—customer ID unique within the project
  2. Additionally you can use thecustomer_email, customer_last_name, customer_first_name parameters—the email address, last and first name of the customer within the project.
  3. To preselect Skrill Wallet as the payment method on Payment Page for customers, pass the code skrill-wallet in the force_payment_method parameter in the request for opening.
  4. If required, you can also add any other additional parameters Payment Page supports. For information about all parameters available in the Skrill Wallet method, see Payment Page invocation parameters.
  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 Skrill Wallet method must include project and payment IDs, the currency and the amount of a payment, as shown in the following example:

EPayWidget.run(
    { payment_id: 'X03936', 
      payment_amount: 5000, 
      payment_currency: 'USD', 
      project_id: 0, 
      customer_id: 'customer1',
      customer_email: 'email@mail.com',
      customer_last_name: 'Johnson',
      customer_first_name: 'John',
      signature: "kUi2x9dKHAVNU0FYldJrxh4yo+52Kt8KU+Y1YO\/RLCvhtT4DqtVUkDJrOcZzUCwX6R\/ekpZhkIQg=="
    }
)

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

Callback format

The Skrill Wallet 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 50,00 USD purchase from the account account@customer.com made by the customer 207 in the 68 project.

Figure: Example of a successful purchase callback

{
        "project_id": 68,
        "payment": {
            "id": "86526901942",
            "type": "purchase",
            "status": "success",
            "date": "2019-07-10T08:51:14+0000",
            "method": "skrill",
            "sum": {
                "amount": 5000,
                "currency": "USD"
            },
            "description": "Deposit"
        },
        "account": {
            "number": "account@customer.com"
        },
        "customer": {
            "id": "207"
        },
        "operation": {
            "id": 21547000003559,
            "type": "sale",
            "status": "success",
            "date": "2019-07-10T08:51:14+0000",
            "created_date": "2019-07-10T08:50:59+0000",
            "request_id": "arsthbvcab34",
            "sum_initial": {
                "amount": 5000,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 5000,
                "currency": "USD"
            },
            "provider": {
                "id": 1132,
                "payment_id": "",
                "date": "2019-07-10T08:51:13+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "Dnr3zBWrTAnz1C6fpYDZoywD0R263VToYoJBPGlNeZ/KOcha4H4VGx3eMaO8A0IfvQ=="
    }

The following is the example of a callback for a purchase declined due to insufficient funds on customer account.

Figure: Example of a declined purchase callback

{
        "project_id": 68,
        "payment": {
            "id": "15626281690123599",
            "type": "purchase",
            "status": "decline",
            "date": "2019-07-09T23:22:59+0000",
            "method": "skrill",
            "sum": {
                "amount": 10000,
                "currency": "USD"
            },
            "description": "Deposit"
        },
        "customer": {
            "id": "207"
        },
        "operation": {
            "id": 21531000003532,
            "type": "sale",
            "status": "decline",
            "date": "2019-07-09T23:22:59+0000",
            "created_date": "2019-07-08T23:22:54+0000",
            "request_id": "6e3cf13e8a76",
            "sum_initial": {
                "amount": 10000,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "USD"
            },
            "provider": {
                "id": 1132,
                "payment_id": "",
                "date": "2019-07-08T23:22:56+0000",
                "auth_code": ""
            },
            "code": "20105",
            "message": "Insufficient funds on customer account"
        },
        "signature": "AiXDW6GnzyvtjMq2siDsCNkay+SPkvIo7d7e+t9i8nCh5p/d3JYL=="
    }

Related topics

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

Purchases by using Gate

General information

In the Skrill Wallet 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 redirecting customer to the Skrill Wallet service.
  3. Get the callback with the payment result from the payment platform.

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



Figure: Purchase sequence by using Gate

  1. A customer initiates a purchase through Skrill Wallet 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 Skrill Wallet service.
  7. The request is processed on the Skrill Wallet side.
  8. The Skrill Wallet service sends the data for redirecting the customer to the Skrill Wallet 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 Skrill Wallet service.
  11. The customer completes all the payment steps required.
  12. The payment is processed on the Skrill Wallet side.
  13. The result is displayed to the customer.
  14. The customer is redirected to the merchant's web service.
  15. The Skrill Wallet service sends the payment result notification to the payment platform.
  16. The ECommPay 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 Skrill Wallet payment method and provide the information about formats of the data for redirecting customers and the information about the format of callbacks with payment results. The general information about working with API see in the API Description section.

Request format

There are several things you must consider when using purchase requests in the Skrill Wallet method:
  1. You perform purchase by sending the request to /v2/payment/wallet/skrill/sale by using POST (HTTP) method. This request refers to the payment by using e-wallets request group: /v2/payment/wallet/{payment_method}/sale.
  2. The following objects and parameters must be specified in the request:
    • Object general—general purchase information:
      • project_id—project identifier
      • payment_id—unique payout 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 ID of the customer within the merchant project
      • email—email address
      • first_name—first name
      • last_name—last name
      • ip_address—customer IP address
    • Object payment—purchase information:
      • amount—purchase amount
      • currency—purchase currency in the ISO-4217 alpha-3 format
    • return_url—URL for returning customers to the merchant site:
      • success — after successfully passed payment
      • decline—after declined payment
      • return—common return URL
  3. If required, you can also add any other additional parameters Gate supports.

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

Figure: Purchase request example

{
  "general": {
    "project_id": 238,
    "payment_id": "SKRILL_SALE_12345",
    "signature": "t8qap+aD70GdZwlTW93kFCOqaWXP/AITLKLkN4Tkd73UfSt9F7dni4/9WWIYcBZEL=="
  },
  "customer": {
    "ip_address": "127.0.0.1",
    "customer_email": "email@mail.com",
    "customer_last_name": "Johnson",
    "customer_first_name": "John",
    "id": "123"
  },
  "payment": {
    "amount": 5000,
    "currency": "USD",
    "description": "skrill payment"
  },
  "return_url": {
    "success": "http://merchant.com",
    "decline": "http://merchant.com"
  }
}

Formats of the customer redirection data

To redirect a customer from the web service to the Skrill Wallet 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://pay.skrill.com/app/?sid=2b41879aed9151d047b9905d"

Callback format

The Skrill Wallet 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 50,00 USD purchase from the account account@customer.com made by the customer 207 in the 68 project.

Figure: Example of a successful purchase callback

{
        "project_id": 68,
        "payment": {
            "id": "86526901942",
            "type": "purchase",
            "status": "success",
            "date": "2019-07-10T08:51:14+0000",
            "method": "skrill",
            "sum": {
                "amount": 5000,
                "currency": "USD"
            },
            "description": "Deposit"
        },
        "account": {
            "number": "account@customer.com"
        },
        "customer": {
            "id": "207"
        },
        "operation": {
            "id": 21547000003559,
            "type": "sale",
            "status": "success",
            "date": "2019-07-10T08:51:14+0000",
            "created_date": "2019-07-10T08:50:59+0000",
            "request_id": "arsthbvcab34",
            "sum_initial": {
                "amount": 5000,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 5000,
                "currency": "USD"
            },
            "provider": {
                "id": 1132,
                "payment_id": "",
                "date": "2019-07-10T08:51:13+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "Dnr3zBWrTAnz1C6fpYDZoywD0R263VToYoJBPGlNeZ/KOcha4H4VGx3eMaO8A0IfvQ=="
    }

The following is the example of a callback for a purchase declined due to insufficient funds on customer account.

Figure: Example of a declined purchase callback

{
        "project_id": 68,
        "payment": {
            "id": "15626281690123599",
            "type": "purchase",
            "status": "decline",
            "date": "2019-07-09T23:22:59+0000",
            "method": "skrill",
            "sum": {
                "amount": 10000,
                "currency": "USD"
            },
            "description": "Deposit"
        },
        "customer": {
            "id": "207"
        },
        "operation": {
            "id": 21531000003532,
            "type": "sale",
            "status": "decline",
            "date": "2019-07-09T23:22:59+0000",
            "created_date": "2019-07-08T23:22:54+0000",
            "request_id": "6e3cf13e8a76",
            "sum_initial": {
                "amount": 10000,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "USD"
            },
            "provider": {
                "id": 1132,
                "payment_id": "",
                "date": "2019-07-08T23:22:56+0000",
                "auth_code": ""
            },
            "code": "20105",
            "message": "Insufficient funds on customer account"
        },
        "signature": "AiXDW6GnzyvtjMq2siDsCNkay+SPkvIo7d7e+t9i8nCh5p/d3JYL=="
    }

Related topics

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

COF purchases by using Gate

General information

The Skrill Wallet payment method provides the ability to perform COF purchases of two types: OneClick and regular payments. For more information about COF purchases, see Credential-on-file (COF) purchases.

In the Skrill Wallet payment method, COF purchases of the OneClick type are performed by using the Skrill 1-Tap service. This service allows to make payments in "one tap" using previously saved wallet.

COF payment registration

To register a COF payment by using Gate, the merchant is required to send a request for purchase with all the required parameters, signature, and the COF purchase registration parameter recurring.register: true to the ECommPay URL and get the callback with the payment result from the payment platform. To register a regular payment the request should also contain information about the frequency, amount, start and end dates of the regular payments.

In the COF purchase registration callback you receive its identifier, which you can use to perform OneClick payments, and to update, change conditions or cancel regular payments.

For more information about purchase processing by using Gate, see Purchases by using Gate.

COF purchase performing

After the payment is registered, customers can initiate a OneClick payment using the Skrill 1-Tap service, or the funds are debited automatically according to the specified regular payment conditions.

Updating of the regular payments performing conditions

At any time, you can change the conditions of regular payments, for example, change the execution time, the expiration date or the amount of debits. When conditions change, the actual withdrawal of funds from the customer account does not occur.

Cancellation of the regular payments performing

Until the expiration date of regular payments performing, you can cancel it.

The sections that follow discuss in more details the requests formats and parameters to use in the Skrill Wallet payment method and the information about the format of callbacks with payment results. The general information about working with API see in the API Description section.

Requests format

There are several things you must consider when performing COF purchases in the Skrill Wallet method:
  1. You can perform COF purchases by sending the following requests by using POST (HTTP) method:
  2. The following objects and parameters must be specified in the request:
    • Object general—general purchase information:
      • project_id—project identifier
      • payment_id—unique payout 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 ID of the customer within the merchant project
      • ip_address—customer IP address
    • Object payment—purchase information:
      • amount—purchase amount
      • currency—purchase currency in the ISO-4217 alpha-3 format
    • Object recurring—COF purchase information:
      • register—payment registration as a COF purchase (regular or OneClick)
      • id—registered COF purchase identifier
      • start_date—the start date of regular payments, in the DD-MM-YYYY format (must be at least one day later than the date of registration)
      • expiry_year—regular payments end year
      • expiry_month—regular payments end month
      • expiry_day—regular payments end day
      • amount—amount of debiting
      • period—regular payment performing period
      • interval— regular payment performing interval
      • time—regular payment performing time in the hh:mm:ss (UTC0) format

      The required parameters in the recurring object depend on the type of request. For more information, see the API specification.

  3. If required, you can also add any other additional parameters Gate supports.

A correct COF purchase registration request through the Skrill Wallet method must include project and payment IDs, customer IP-address, signature, currency and amount of the purchase, as well as the registration parameter and the conditions for regular payments, as shown in the following example:

Figure: OneClick payment registration request example

 {
  "general": {
    "project_id": 238,
    "payment_id": "TEST_15427007172789",
    "signature": "DH0v2pZnkK9hwytQ6/ZtDSQh+wwx/OqrWdbltzO5GMSkzd0Iq6lM2v8rmWQV4sbP+4A==",
  },
  "customer": {
    "ip_address": "87.245.207.226",
    "id": "123"
  },
  "payment": {
    "amount": 1000,
    "currency": "EUR"
  },
  "recurring": {
    "register": true
  }
}

Figure: Regular payment registration request example

 {
  "general": {
    "project_id": 238,
    "payment_id": "TEST_15427007172789",
    "signature": "DH0v2pZnkK9hwytQ6/ZtDSQh+wwx/OqrWdbltzO5GMSkzd0Iq6lM2v8rmWQV4sbP+4A==",
  },
  "customer": {
    "ip_address": "87.245.207.226"
  },
  "payment": {
    "amount": 1000,
    "currency": "EUR"
  },
  "recurring": {
    "register": true,
    "amount": 1000,
    "interval": 1,
    "cycle": "week",
    "start_date": "21-11-2018",
    "expiry_year": 2025,
    "expiry_month": 11,
    "expiry_day": 25
  }
}
A correct COF purchase performing request through the Skrill Wallet method must include project and payment IDs, customer IP-address, signature, currency and amount of the purchase, as well as the COF payment identifier, as shown in the following example:

Figure: OneClick payment performing request example

 {
  "general": {
    "project_id": 238,
    "payment_id": "TEST_15427007172789",
    "signature": "DH0v2pZnkK9hwytQ6/ZtDSQh+wwx/OqrWdbltzO5GMSkzd0Iq6lM2v8rmWQV4sbP+4A==",
  },
  "customer": {
    "ip_address": "87.245.207.226"
  },
  "payment": {
    "amount": 1000,
    "currency": "EUR"
  },
  "recurring": {
    "id": 1234567890
  }
}
A correct regular payment conditions updating request through the Skrill Wallet method must include project and payment IDs, customer IP-address, signature, currency and amount of the purchase, as well as the COF purchase identifier and conditions parameters, as shown in the following example:

Figure: Regular payment conditions updating request example

 {
  "general": {
    "project_id": 238,
    "payment_id": "TEST_15427007172789",
    "signature": "DH0v2pZnkK9hwytQ6/ZtDSQh+wwx/OqrWdbltzO5GMSkzd0Iq6lM2v8rmWQV4sbP+4A==",
  },
  "customer": {
    "ip_address": "87.245.207.226"
  },
  "payment": {
    "amount": 1000,
    "currency": "EUR"
  },
  "recurring": {
    "id": 1234567890
  }
}
A correct regular payment cancellation request through the Skrill Wallet method must include project and payment IDs, customer IP-address, signature, currency and amount of the purchase, as well as the COF purchase identifier, as shown in the following example:

Figure: Regular payment cancellation request example

 {
  "general": {
    "project_id": 238,
    "payment_id": "TEST_15427007172789",
    "signature": "DH0v2pZnkK9hwytQ6/ZtDSQh+wwx/OqrWdbltzO5GMSkzd0Iq6lM2v8rmWQV4sbP+4A==",
  },
  "customer": {
    "ip_address": "87.245.207.226"
  },
  "payment": {
    "amount": 1000,
    "currency": "EUR"
  },
  "recurring": {
    "id": 1234567890
  }
}

Callback format

The standard format for callbacks is used to deliver the results of actions with COF purchases. For more information, see Callbacks.

The following is the example of a callback with an information about COF purchase registration for a customer in the 238 project.

Figure: Example of succeed COF purchase registration

 {
        "project_id": 238,
        "payment": {
            "id": "SKRILL_1TAP",
            "type": "recurring",
            "status": "success",
            "date": "2018-11-20T08:44:46+0000",
            "method": "skrill",
            "sum": {
                "amount": 300,
                "currency": "EUR"
            },
            "description": "skrill payment"
        },
        "account": {
            "number": "customer@mail.com"
        },
        "recurring": {
            "id": 1000030038,
            "currency": "EUR",
            "valid_thru": "-0001-11-30T00:00:00+0000"
        },
        "operation": {
            "id": 1000034,
            "type": "recurring",
            "status": "success",
            "date": "2018-11-20T08:44:46+0000",
            "created_date": "2018-11-20T08:44:41+0000",
            "request_id": "07fd7ade7cf010",
            "sum_initial": {
                "amount": 300,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 300,
                "currency": "EUR"
            },
            "provider": {
                "id": 1132,
                "payment_id": "2548950091",
                "date": "2018-11-20T08:44:45+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "x2tsnvLCRXZMX8Kwyr9a8+I3RipuPWUod5c89cDSQ6cRq/yx56uZb7MTMdDEEg4w=="
    }

The following is the example of a callback after regular payment conditions updating.

Figure: Example of regular payment conditions updating callback

{
        "project_id": 238,
        "payment": {
            "id": "SKRILL_SALE_ID",
            "type": "purchase",
            "status": "success",
            "date": "2018-11-22T07:05:56+0000",
            "method": "skrill",
            "sum": {
                "amount": 100,
                "currency": "EUR"
            },
            "description": "skrill payment"
        },
        "recurring": {
            "id": 1000034,
            "currency": "EUR",
            "valid_thru": "2018-11-29T00:00:00+0000"
        },
        "operation": {
            "id": 1972,
            "type": "recurring_update",
            "status": "success",
            "date": "2018-11-22T07:09:18+0000",
            "created_date": "2018-11-22T07:09:16+0000",
            "request_id": "ab70b4f9643bb0b",
            "sum_initial": {
                "amount": 0,
                "currency": ""
            },
            "sum_converted": {
                "amount": 0,
                "currency": ""
            },
            "provider": {
                "id": 1132,
                "payment_id": "",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "dVpS1keJ0Bf0ofZSLhwJm3rr0Oh534I+8lPJ42BRcAak+1nLPlD9rkjcKYUEtgpsMA=="
    }

The following is the example of a callback after regular payment cancellation.

Figure: Example of regular payment cancellation callback

  {
        "project_id": 238,
        "payment": {
            "id": "SKRILL_SALE_ID",
            "type": "purchase",
            "status": "success",
            "date": "2018-11-22T07:05:56+0000",
            "method": "skrill",
            "sum": {
                "amount": 100,
                "currency": "EUR"
            },
            "description": "skrill payment"
        },
        "recurring": {
            "id": 1000034,
            "currency": "EUR",
            "valid_thru": "2018-11-29T00:00:00+0000"
        },
        "operation": {
            "id": 1973,
            "type": "recurring_cancel",
            "status": "success",
            "date": "2018-11-22T07:14:51+0000",
            "created_date": "2018-11-22T07:14:50+0000",
            "request_id": "8d5ea1f970faaa76c4d10",
            "sum_initial": {
                "amount": 0,
                "currency": ""
            },
            "sum_converted": {
                "amount": 0,
                "currency": ""
            },
            "provider": {
                "id": 1132,
                "payment_id": "",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "QHS5h1BVZqHS39wlzC0pfgSZZAhZVA6ZLDnyP1JAWHM0irFE/Lt3dMTizyQsossGDUVMAQ=="
    }

The following is the example of a callback with an information about declined COF purchase registration.

Figure: Example of declined COF purchase registration

{
        "project_id": 238,
        "payment": {
            "id": "123456",
            "type": "recurring",
            "status": "decline",
            "date": "2018-11-15T07:17:08+0000",
            "method": "skrill",
            "sum": {
                "amount": 200,
                "currency": "EUR"
            },
            "description": "skrill payment"
        },
        "errors": [
            {
                "code": "2701",
                "message": "Rules Failed Code",
                "description": "fatal: RULES_FAILED_CODE"
            }
        ],
        "recurring": {
            "id": 100070,
            "currency": "EUR",
            "valid_thru": "-0001-11-30T00:00:00+0000"
        },
        "operation": {
            "id": 10001868,
            "type": "recurring",
            "status": "decline",
            "date": "2018-11-15T07:17:08+0000",
            "created_date": "2018-11-15T07:17:08+0000",
            "request_id": "e5ee540d420d6ccd",
            "sum_initial": {
                "amount": 200,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 200,
                "currency": "EUR"
            },
            "provider": {
                "id": 1132,
                "payment_id": ""
            },
            "code": "2701",
            "message": "Rules Failed Code"
        },
        "signature": "SgrlW4XHS8dJdGW3lDLacXdwe4L5Mvg3SjFEoViCg9k04OqTBaNimdWxwwXYGjCsFI5ig=="
    }

Related topics

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

Refunds by using Gate

General information

Skrill Wallet supports full and partial refunds processing. To perform a refund through the Skrill Wallet 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 refund process is provided below.



Figure: Refund sequence by using Gate

  1. A customer orders a refund on the merchant's web service side.
  2. Merchant's web service sends the request for the refund 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 refund request to the Skrill Wallet service.
  7. The payment is processed on the Skrill Wallet side.
  8. Skrill Wallet 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 refund result from the web service.

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

Request format

There are several things you must consider when using refund requests in the Skrill Wallet method:
  1. You perform refund by sending the request to /v2/payment/skrill/refund by using POST (HTTP) method.
  2. The following objects and parameters must be specified in any request:
    • Object general—general refund information:
      • project_id—project identifier
      • payment_id—unique refund 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:
      • ip_address—customer IP address
      • id—identifier in the project
    • Object account—customer account information:
      • number—email address linked to the wallet or account number;
    • Object payment—refund information:
      • description—comment or description
      • amount—refund amount in minor units (mandatory for partial refund only)
      • currency—refund currency in ISO-4217 alpha-3 format (mandatory for partial refund only)
  3. If you need to make a partial refund, pass the amount in the payment.amount parameter.
  4. If required, you can also add any other additional parameters Gate supports.

Thus, a correct refund request in the Skrill Wallet method must include project and payment IDs, customer IP address, currency and amount of the refund, as shown in the following example:

Figure: Example of a refund request

{
   "general": {    
    "project_id": 239,    
    "payment_id": "refund_02",   
    "signature": "of8k9xerKSK4XL1QFaDH3p9Mh0CIcjmOwSwKJ7KLTZYO56lCv+f1M0Sf/7eg=="
  },  
   "customer": {    
     "ip_address": "1.2.3.4",
     "id": "123456" 
  },  
   "account": {    
     "number": "customer@mail.com"
  },  
   "payment": {    
     "amount": 10000,    
     "currency": "USD",
     "description": "refund_02"
 }
}

Callback format

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

The following is the example of a callback with an information about successful 5,00 USD refund for the customer account 98330562 in the 238 project.

Figure: Example of a successful refund callback

{
        "project_id": 238,
        "payment": {
            "id": "TEST_1540911136903",
            "type": "purchase",
            "status": "partially refunded",
            "date": "2018-10-31T10:21:50+0000",
            "method": "skrill",
            "sum": {
                "amount": 1000,
                "currency": "USD"
            },
            "description": "TEST_1540911136903"
        },
        "account": {
            "number": "98330562"
        },
        "customer": {
            "id": "1"
        },
        "operation": {
            "id": 19050000001772,
            "type": "refund",
            "status": "success",
            "date": "2018-10-31T10:21:50+0000",
            "created_date": "2018-10-31T10:21:48+0000",
            "request_id": "798451cf786ffd28",
            "sum_initial": {
                "amount": 500,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 500,
                "currency": "USD"
            },
            "provider": {
                "id": 1132,
                "payment_id": "2528878875",
                "date": "2018-10-31T10:21:50+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "h7/6IhL12R8LtOGDG0sC6XrYQCbik/kj1iac2wMcqzJ84wheaiSZHCy+o/QycuAUw=="
    }
}

The following is the example of a callback for a refund declined due to the refund amount is more than init amount.

Figure: Example of a declined refund callback

{
        "project_id": 238,
        "payment": {
            "id": "TEST_1540911136903",
            "type": "purchase",
            "status": "success",
            "date": "2018-10-31T09:37:02+0000",
            "method": "skrill",
            "sum": {
                "amount": 1000,
                "currency": "USD"
            },
            "description": "TEST_1540911136903"
        },
        "account": {
            "number": "98330562"
        },
        "customer": {
            "id": "1"
        },
        "operation": {
            "id": 19050000001771,
            "type": "refund",
            "status": "decline",
            "date": "2018-10-31T10:18:52+0000",
            "created_date": "2018-10-31T10:18:50+0000",
            "request_id": "f93d3a958efde05af646e9e010907bef3729e97e-3348b16c3138eba52c8621b1a16f1312b90dab09",
            "sum_initial": {
                "amount": 2000,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 2000,
                "currency": "USD"
            },
            "provider": {
                "id": 1132,
                "payment_id": "",
                "date": "2018-10-31T10:18:51+0000",
                "auth_code": ""
            },
            "code": "3283",
            "message": "Refund amount more than init amount"
        },
        "signature": "tKGW0j0R9BqygpoGALoBxh+ABZZ603C9JPMAQdg8wRhHVtSZ2UI3B7mBPb0U56f56vyl2IzHyK+c18LdhiDqrA=="
    }

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 Skrill Wallet 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 sequence by using Gate

  1. A customer orders a payout through the Skrill Wallet system.
  2. Merchant's 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 Skrill Wallet service.
  7. The payout is processed on the Skrill Wallet side.
  8. Skrill Wallet 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 payout result from the web service.

The sections that follow discuss in more details the request format and the Gate parameters to use in the Skrill Wallet payment method and provide the information on the format of callbacks with payout results. The general information about working with API see in the API Description section.

Request format

There are several things you must consider when using payout requests in the Skrill Wallet method:
  1. You perform payouts by sending the /v2/payment/skrill/payout request by using POST (HTTP) method.
  2. The following objects and parameters must be specified in any request:
    • Object general—general payout information:
      • project_id—project identifier
      • payment_id—unique payout 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—identifier
      • ip_address—customer IP address
    • Object account—customer account information:
      • number—account number;
    • Object payment—payout information:
      • amount—payout amount
      • currency—purchase currency in the ISO-4217 alpha-3 format
  3. If required, you can also add any other additional parameters Gate supports.

Thus, a correct payout request in the Skrill Wallet method must include project, customer, and payment IDs, customer IP address, currency and amount of the payout, the account number for funds crediting, as shown in the following example:

Figure: Example of a payout request

{
    "general": {
        "project_id": 35,
        "payment_id": "Payment 12",
        "signature": "2tlMuYxLW9Yu6RETr8pdCfmi0Uguu0BQjXWH6naCA9Ts6o4EVPjLyfbOQ+9ajAteg5lPk96Q=="
  },
    "customer": {
        "id": "207",
        "ip_address": "1.1.1.1" 
  },
    "payment": {
        "amount": 5000,
        "currency": "USD"
  },
    "account": {
        "number": "account@customer.com"
  }
}

Callback format

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

The following is the example of a callback with an information about successful 50,00 USD payout made for the 207 customer ID in the 68 project.

Figure: Example of a successful payout callback

{
        "project_id": 68,
        "payment": {
            "id": "86526901942",
            "type": "payout",
            "status": "success",
            "date": "2019-07-10T08:51:14+0000",
            "method": "skrill",
            "sum": {
                "amount": 5000,
                "currency": "USD"
            },
            "description": "Credit"
        },
        "account": {
            "number": "account@customer.com"
        },
        "customer": {
            "id": "207"
        },
        "operation": {
            "id": 21547000003559,
            "type": "payout",
            "status": "success",
            "date": "2019-07-10T08:51:14+0000",
            "created_date": "2019-07-10T08:50:59+0000",
            "request_id": "arsthbvcab34",
            "sum_initial": {
                "amount": 5000,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 5000,
                "currency": "USD"
            },
            "provider": {
                "id": 1132,
                "payment_id": "",
                "date": "2019-07-10T08:51:13+0000",
                "auth_code": ""
            },
            "code": "0",
            "message": "Success"
        },
        "signature": "Dnr3zBWrTAnz1C6fpYDZoywD0R263VToYoJBPGlNeZ/KOcha4H4VGx3eMaO8A0IfvQ=="
    }

The following is the example of a callback for a payout rejected due to error during operation validation process.

Figure: Example of a declined payout callback

{
        "project_id": 68,
        "payment": {
            "id": "15626281690123599",
            "type": "payout",
            "status": "decline",
            "date": "2019-07-09T23:22:59+0000",
            "method": "skrill",
            "sum": {
                "amount": 10000,
                "currency": "USD"
            },
            "description": "Credit"
        },
        "customer": {
            "id": "81801"
        },
         "account": {
            "number": " jwrangler889@gmail.com"
        },
        "operation": {
            "id": 21531000003532,
            "type": "payout",
            "status": "decline",
            "date": "2019-07-09T23:22:59+0000",
            "created_date": "2019-07-08T23:22:54+0000",
            "request_id": "6e3cf13e8a76",
            "sum_initial": {
                "amount": 10000,
                "currency": "USD"
            },
            "sum_converted": {
                "amount": 10000,
                "currency": "USD"
            },
            "provider": {
                "id": 1132,
                "payment_id": "",
                "date": "2019-07-08T23:22:56+0000",
                "auth_code": ""
            },
            "code": "20502",
            "message": "Error during operation validation"
        },
        "signature": "AiXDW6GnzyvtjMq2siDsCNkay+SPkvIo7d7e+t9i8nCh5p/d3JYL=="
    }

Related topics

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

Testing

General information

For the Skrill Wallet method the testing of purchases by using Payment Page and Gate, as well as refunds, payouts and OneClick (1-Tap) payments by using Gate is available..

Testing can be performed within a test project, to enable and disable the testing availability, contact ECommPay technical support via support@ecommpay.com.

When performing a test payment, take into account that you must specify the identifier of the test project in the requests. The interfaces of the payment form emulators of Payment Page and Skrill Wallet may differ from the production environment.



Test payments statuses

When testing one-time purchases, the final payment status is determined by the amount specified in the request:

  • decline status with 40000 or 40400 amount
  • success status with any other amount

When testing refunds, the final refund status is determined by the amount specified in the request:

  • decline status with 50000 or 50500 amount
  • success status with any other amount

When testing payouts, the final payment status is determined by the amount specified in the request:

  • decline status with 40000 or 40400 amount
  • success status with any other amount

When testing OneClick payments, the final payment status is determined by the amounts specified in the requests:

  • For registering OneClick payments:
    • decline status with 40000 or 40400 amount
    • success status with any other amount
  • For performing OneClick payments:
    • decline status with 80000 or 80800 amount
    • success status with any other amount

It should also be noted, that processed OneClick payments are assigned different payment_id identifiers, and the same recurring_id identifier.

Purchases by using Payment Page

To perform a test purchase by using Payment Page, do the following:

  1. Send a correct test request for Payment Page opening to the payment platform.
  2. If the skrill-wallet method was not specified in the request—select the method on the emulator page.
  3. Click the Success or Decline button (depending on the amount specified in the request).
  4. Accept a callback with information about the payment result.

The full information about purchase process by using Skrill Wallet through Payment Page is provided in the section Purchases by using Payment Page.

Purchases by using Gate

To perform a test purchase by using Gate, do the following:

  1. Send a correct test request for purchase to the payment platform.
  2. Accept a callback with redirection data.
  3. Go to the received URL and click the Success or Decline button (depending on the amount specified in the request).
  4. Accept a callback with information about the payment result.

The full information about purchase process by using Skrill Wallet through Gate is provided in the section Purchases by using Gate.

OneClick payments by using Gate

To register or perform a test OneClick payment by using Gate, send a correct test request to the payment platform and accept a callback with information about the payment result. Full information about COF purchases by using Skrill Wallet through Gate is provided in the section COF purchases by using Gate.

Refunds by using Gate

To perform a test refund by using Gate, send a correct test request for refund of previously performed test purchase to the payment platform and accept a callback with information about the payment result.

The test refund performing is possible only within a day after the initial purchase. The full information about the refund process by using Skrill Wallet through Gate is provided in the section Refunds by using Gate.

Payouts by using Gate

To perform a test payout by using Gate, send a correct test request to the payment platform and accept a callback with information about the payment result. The full information about payout process by using Skrill Wallet through Gate is provided in the section Payouts by using Gate.

Analysis of payments results

As with other payment methods ECommPay offers, when using the Skrill Wallet 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.