Skrill Wallet

Interaction diagram

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

Operations support

	Interfaces				Amounts *
	Payment Page	Mobile SDKs	Gate	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 Monetix key account manager.

You can check the payment amount limits in your project by using Dashboard. To check your payment amount limits, go to Dashboard, select the Projects section and click the Payment methods tab.

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.

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

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 Monetix 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 methods.

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

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 required for any payment method:
   • project_id—the project ID obtained from Monetix
   • payment_id—payment ID unique within the project
   • payment_currency—payment currency in ISO-4217 alpha-3 format
   • payment_amount—payment amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
   • customer_id—the unique ID of the customer within your project
   • customer_email—customer email
   • customer_first_name—customer first name
   • customer_last_name—customer last name
2. Also, you may need to add the following customer information parameters (Consult with your account manager to learn whether these parameters are mandatory):
   • customer_country—customer country in the ISO 3166-1 alpha-2 format
   • customer_city—city of the customer address
   • customer_zip—customer postal code
   • customer_address—customer address
   • customer_phone—customer phone number
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.

Here is an example of data from a request for Payment Page opening:

EPayWidget.run(
    { 
        payment_id: 'X03936', 
        payment_amount: 5000, 
        payment_currency: 'USD', 
        project_id: 0, 
        customer_id: 'customer1',
        customer_email: 'johndoe@example.com',
        customer_last_name: 'Doe',
        customer_first_name: 'John',
        customer_country: 'GB',
        customer_city: 'Little Whinging',
        customer_zip: '123456',
        customer_address: '4 Privet Drive',
        customer_phone: '12345678901',
        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 in Payment Page.

The following is the example of a callback with an information about successful 50,00 USD purchase from the account johndoe@example.com made by the customer 207 in the 68 project.

{
        "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": "johndoe@example.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.

{
        "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:

• Integration procedure
• Signature generation and verification
• Payment types, operations and payments
• Operation statuses and response codes

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

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

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:
   • general—object with general request identification information:
     • project_id—the project ID you obtained from Monetix
     • 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.
   • customer—object with customer information:
     • id—the unique ID of the customer within your project
     • ip_address—IP address of the customer's device
     • email—customer email
     • first_name—customer first name
     • last_name—customer last name
   • payment—object with purchase information:
     • amount—purchase amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
     • currency—code of purchase currency in the ISO-4217 alpha-3 format
   • return_url—object with the information where to redirect the customer to when the payment is completed or prematurely terminated by the customer:
     • success—the URL to redirect the customer to after the payment is successfully completed
     • decline—the URL to redirect the customer to after the payment is declined
     • return—the URL to redirect the customer to when they prematurely terminate the payment. This URL is also used if the success and decline parameters are not specified in the request
3. Also, you may need to add the following customer information parameters (Consult with your account manager to learn whether these parameters are mandatory):
   • customer—object with customer information:
     • country—customer country in the ISO 3166-1 alpha-2 format
     • city—city of the customer address
     • zip—customer zip code
     • address—customer address
     • phone—customer phone number
4. If required, you can also add any other additional parameters Gate supports.

Here is an example of data from a purchase request in the Skrill Wallet method.

{
    "general": {
        "project_id": 238,
        "payment_id": "SKRILL_SALE_12345",
        "signature": "t8qap+aD70GdZwlTW93kFCOqaWXP/AITLKLkN4Tkd73UfSt9F7dni4/9WWIYcBZEL=="
    },
    "customer": {
        "ip_address": "198.51.100.47",
        "first_name": "John",
        "last_name": "Doe",
        "email": "johndoe@email.com",
        "id": "customer123",
        "country": "GB",
        "city": "Little Whinging",
        "zip": "123456",
        "address": "4 Privet Drive",
        "phone": "12345678901"
    },
    "payment": {
        "amount": 5000,
        "currency": "USD",
        "description": "skrill payment"
    },
    "return_url": {
        "success": "https://example.com/success/",
        "decline": "https://example.com/decline/",
        "return": "https://example.com/return/"
    }
}

Formats of the customer redirection data

After receiving and processing your purchase request, the payment platform sends a callback to your web service containing the data to redirect the customer to the Skrill service.

To redirect the customer, use the values of the following parameters in the redirect_data object:

• url—the URL to redirect the customer to
• body—the data to be sent in the request body
• method—the HTTP method to get an HTML page of the website (for example, POST or GET)
• encrypted—this is the service parameter. Ignore the data it contains.

Here is an example of a piece of callback containing the data to redirect the customer.

"redirect_data": {
    "method": "GET",
    "body": [],
    "encrypted": [],
    "url": "https://example.com/redirect"
}

Callback format

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

The following is the example of a callback with an information about successful 50,00 USD purchase from the account johndoe@example.com made by the customer 207 in the 68 project.

{
        "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": "johndoe@example.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.

{
        "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:

• Integration procedure
• Signature generation and verification
• Payment types, operations and payments
• Operation statuses and response codes

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 you to make payments in "one click" 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 Monetix 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 Purchase 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

1. You can perform COF purchases by sending the following requests by using POST (HTTP) method:
   • /v2/payment/skrill/sale—to register COF purchases
   • /v2/payment/skrill/1-tap—to perform OneClick payments
   • /v2/payment/skrill/recurring/update—to update the regular payments performing conditions
   • /v2/payment/skrill/recurring/cancel—to cancel the regular payments performing
2. The following objects and parameters must be specified in the request:
   • general—object with general request identification information:
     • project_id—the project ID you obtained from Monetix
     • 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.
   • customer—object with customer information:
     • id—the unique ID of the customer within your project
     • ip_address—IP address of the customer's device
     • email—customer email
     • first_name—customer first name
     • last_name—customer last name
   • payment—object with purchase information:
     • amount—purchase amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
     • currency—code of purchase currency in the ISO-4217 alpha-3 format
   • recurring—object with 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 to debit in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
     • 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.

Here is an example of the data from a COF purchase registration request in the Skrill Wallet method.

 {
    "general": {
        "project_id": 238,
        "payment_id": "TEST_15427007172789",
        "signature": "DH0v2pZnkK9hwytQ6/ZtDSQh+wwx/OqrWdbltzO5GMSkzd0Iq6lM2v8rmWQV4sbP+4A==",
    },
    "customer": {
        "ip_address": "87.245.207.226",
        "id": "customer123",
        "first_name": "John",
        "last_name": "Doe",
        "email": "johndoe@example.com"
    },
    "payment": {
        "amount": 1000,
        "currency": "EUR"
    },
    "recurring": {
        "register": true
    }
}

Callback format

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

Related topics

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

• Integration procedure
• Signature generation and verification
• Payment types, operations and payments
• Operation statuses and response codes

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 Monetix URL, and receives a callback with the payment result. The full sequence of the refund process is provided below.

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

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:
   • general—object with 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
   • customer—object with customer information:
     • ip_address—customer device IP
     • id—identifier in the project
   • account—object with customer account information:
     • number—email address linked to the wallet or account number;
   • payment—object with refund information:
     • description—comment or description
     • amount—refund amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.

       The parameter is required only for partial refund.

     • currency—refund currency in ISO-4217 alpha-3 format.

       The parameter is required only for partial refund.

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.

Here is an example of the data from a refund request in the Skrill Wallet method.

{
   "general": {    
    "project_id": 239,    
    "payment_id": "refund_02",   
    "signature": "of8k9xerKSK4XL1QFaDH3p9Mh0CIcjmOwSwKJ7KLTZYO56lCv+f1M0Sf/7eg=="
  },  
   "customer": {    
     "ip_address": "198.51.100.47",
     "id": "123456" 
  },  
   "account": {    
     "number": "johndoe@example.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 in Gate.

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.

{
        "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.

{
        "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:

• Integration procedure
• Signature generation and verification
• Payment types, operations and payments
• Operation statuses and response codes

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 Monetix URL, and receives a callback with the payment result. The full sequence of the payout process is provided below.

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

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:
   • general—object with general request identification information:
     • project_id—the project ID obtained from Monetix
     • 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.
   • customer—object with customer information:
     • id—the unique ID of the customer within your project
     • ip_address—IP address of the customer's device
     • first_name—customer first name
     • last_name—customer last name
     • email—customer email
   • account—object with customer account information:
     • number—customer account number
   • payment—object with payout information:
     • amount—payout amount in minor currency units without any decimal point or comma except for cases where the currency does not have any minor currency units. If the currency has no minor units (that is, the number of digits for minor currency units is zero), then you must set this parameter to the amount in the major currency units. For the information on whether the currency has any minor units, see Currency codes.
     • currency—code of payout currency in the ISO-4217 alpha-3 format
3. If required, you can also add any other additional parameters Gate supports.

Here is an example of data from a payout request in the Skrill Wallet method.

{
    "general": {
        "project_id": 35,
        "payment_id": "Payment 12",
        "signature": "2tlMuYxLW9Yu6RETr8pdCfmi0Uguu0BQjXWH6naCA9Ts6o4EVPjLyfbOQ+9ajAteg5lPk96Q=="
  },
    "customer": {
        "id": "207",
        "ip_address": "198.51.100.47",
        "first_name": "John",
        "last_name": "Doe",
        "email": "johndoe@example.com" 
  },
    "payment": {
        "amount": 5000,
        "currency": "USD"
  },
    "account": {
        "number": "johndoe@example.com"
  }
}

Callback format

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

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.

{
        "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": "johndoe@example.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.

{
        "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": "johndoe@example.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:

• Integration procedure
• Signature generation and verification
• Payment types, operations and payments
• Operation statuses and response codes

• single payout—you specify the currency and amount for a payout available for this method and fill in all the fields required for the selected payment method on the Dashboard pages.
• as a part of a mass payment—all the parameters are specified in a CSV file. Refer to the Payouts by using Gate section for the parameters required by your payment method.

Information about completed payouts is available for viewing in the Payments and Manual Payments sections of Dashboard.

For more information about payout processing by using Dashboard, see Performing payouts.

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 Monetix technical support via support@monetix.pro.

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

Testing purchase 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 Purchase by using Payment Page.

Testing purchase 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 Purchase by using Gate.

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

Testing refund 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 Refund by using Gate.

Testing payout 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 Payout by using Gate.

As with other payment methods Monetix offers, when using this method, you have several options to analyze the information about payments and operations.

You can load and analyze all the necessary information in Dashboard (dash-light.trxhost.com), for instance you can use the analytic panels in the Analytics section for this purpose.

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 format by using the tools in the Reports section. You can perform export as a one-time or regular download of data to your local computer.
• 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 means of sending requests to the /operations/get endpoint.

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