Account and Integration Options

You can use the following account and integration options:

• Secure Return URL parameter
• Merchant refunds
• Chargeback notification
• Adding a descriptor

note

Code integration examples describes how to generate a session identifier and redirect the customer to Skrill.

Secure Return URL Parameter

A secure return_url parameter allows you to be certain that the customer has arrived at your return_url page by completing the payment process, rather than by looking up the return_url value in the page source code and entering it into their browser. However, this function only guarantees that the customer has completed the payment process, not that the payment had been processed. If this feature is not activated, please contact Skrill Merchant Services. You must submit the following parameters with each transaction:

• return_url
• transaction_id
• secret word (this will be automatically submitted if entered in the Settings > Developer Settings section in your Skrill account).

Skrill will then add the following parameters to the return_url:

Parameter	Description	Example value
transaction_id	The transaction_id you submitted.	A205220
msid	The MD5 signature, with the following values: - merchant_id (e.g., 123456) - transaction_id (e.g., A205220) - upper-case MD5 value of the ASCII equivalent of your secret word	730743ed4ef7ec631155f5e15d2f4fa0

The following are two examples of the secure return_url, using the values above.

Example 1: Merchant submits return_url without additional parameters

https://example.com/return_url.cgi

In this case Skrill will redirect the customer to: https://example.com/return_url.cgi?transaction_id=A205220&msid=730743ed4ef7ec631155f5e15d2f4fa0

Example 2: Merchant submits the return_url with additional parameters

https://example.com/return_url.cgi?par1=val1&par2=val2

In this case Skrill will redirect the customer to: https://example.com/return_url.cgi?par1=val1&par2=val2&transaction_id=A205220&msid=730743ed4ef7ec631155f5e15d2f4fa0

Merchant Refunds

This option enables you to refund a payment to the customer's Skrill account, credit/debit card or bank account (depending on the original payment method used). If this feature is not activated, please contact merchantservices@skrill.com.

note

If your account is configured to allow refunds, you will have an additional action link in the transaction history next to each entry that will trigger a refund to the customer.

You can also make refundsthrough Skrill's Automated PaymentsInterface (API). For details, see the Automated Payments and Merchant Query Interfaces Guide.

Chargeback Notification

When Skrill receives a chargeback request from the provider, a chargeback notification is sent to your status_url page and an email is sent to the primary email address linked to your merchant Skrill account. The status code sent to the status_url page is -3. (For a description of transaction status values, see Transaction status)

Adding a Descriptor

When a customer pays through Skrill, Skrill submits a descriptor with the transaction, containing your business trading/brand name. The descriptor is typically displayed on the bank or credit card statement of the customer. If you want to change this descriptor, please contact merchantservices@skrill.com. Thisfunctionality is only available for the following payment methods:

• Alipay
• Blik
• CVS
• EPS
• ePay
• Dollar General
• iDEAL
• Khipu
• MACH
• Mastercard
• MB Way
• MULTIBANCO
• MyBank
• PagoEfectivo
• PaysafeCard
• PaysafeCash
• PIX
• Przelewy24
• Rapid Transfer
• SPEI
• Visa

note

This feature is not available for cards from out-of-region banks.

For SOFORT you can also submit an additional payment form parameter, dynamic_descriptor, which will override the default value stored by Skrill.

Code Integration examples

You can use the examples below to generate your session ID from Skrill, which is the recommended method for connecting to Quick Checkout, as described in Secure redirection method.

Generating the Session Identifier

Below are examples of how to generate a SID using different programming methods.

Bash

curl -X POST https://pay.skrill.com
  -d "pay_to_email=merchant_email@mail.com"
  -d "amount=10.99"
  -d "currency=EUR"
  -d "language=EN"
  -d "prepare_only=1"

Ruby

require 'net/http'
require 'net/https'
require 'uri'
uri = URI('https://pay.skrill.com')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
req = Net::HTTP::Post.new(uri.path)
req.set_form_data({
  'pay_to_email'=>'merchant_email@mail.com',
  'amount'=>'10.99',
  'currency'=>'EUR',
  'language'=>'EN',
  'prepare_only'=>'1'
})
res = http.request(req)
puts res.body

Redirecting the Customer to Skrill

Once you have the session identifier (SID), you have to redirect the customer to Skrill, and include the session identifier.
https://pay.skrill.com?sid=<SESSION_ID>
where <SESSION_ID> is the SID returned by Skrill.