# Satispay {#pm_satispay}

**Parent topic:**[Digital wallet payments](en_pm_ewallet.md)

## Overview {#en_pm_satispay_overview}

An article about the payment method which allows you to process payments in euros by using e-wallets in different European countries and supports purchases and refunds.

### Introduction {#section_t5z_rlg_ytb .section}

Satispay is a payment method which allows you to process payments in euros by using e-wallets in different European countries.This method supports purchases and refunds.

This article provides information about working with the Satispay method: general insights are presented in the Overview section, while information about the actions required to process payments and perform other actions is presented in the sections that follow.

### General information {#section_tbf_2zk_ggb .section}

|Payment method type|digital wallet payments|
|Payment instruments|digital wallets|
|Countries and regions|[AT](references/en/countries/AT.md), [BE](references/en/countries/BE.md), [BG](references/en/countries/BG.md), [HR](references/en/countries/HR.md), [CY](references/en/countries/CY.md), [CZ](references/en/countries/CZ.md), [DK](references/en/countries/DK.md), [EE](references/en/countries/EE.md), [FI](references/en/countries/FI.md), [FR](references/en/countries/FR.md), [DE](references/en/countries/DE.md), [GR](references/en/countries/GR.md), [HU](references/en/countries/HU.md), [IS](references/en/countries/IS.md), [IE](references/en/countries/IE.md), [IT](references/en/countries/IT.md), [LV](references/en/countries/LV.md), [LI](references/en/countries/LI.md), [LT](references/en/countries/LT.md), [LU](references/en/countries/LU.md), [MT](references/en/countries/MT.md), [NL](references/en/countries/NL.md), [NO](references/en/countries/NO.md), [PL](references/en/countries/PL.md), [PT](references/en/countries/PT.md), [RO](references/en/countries/RO.md), [SK](references/en/countries/SK.md), [SI](references/en/countries/SI.md), [ES](references/en/countries/ES.md), [SE](references/en/countries/SE.md), [CH](references/en/countries/CH.md), [GB](references/en/countries/GB.md)|
|Payment currencies|[EUR](references/en/currencies/EUR.md)|
|Currency conversion|on the Ecommpay side|
|One-time purchases|+|
|Credential-on-file purchases|–|
|Full refunds|+|
|Partial refunds|+|
|Payouts|–|
|Chargebacks|–|
|Notes|–|
|Onboarding and access fee|refer to your Ecommpay account manager|

### Interaction diagram {#section_tsp_gzk_ggb .section}

Payment processing by using the Satispay method involves the merchant's web service, one of Ecommpay interfaces, the Ecommpay payment platform, and technical facilities of the Satispay service.

![](images/pm/en_satispay_functional.svg)

### Operations support {#section_rnx_4cl_ggb .section}

Various platform interfaces can be used to process payments and perform operations using the Satispay method. Purchases can be processed by using Payment Page, Gate and Dashboard \(using payment links\), refunds—by using Gate and Dashboard. At the same time, regardless of the interfaces used, the following properties and limitations are applicable.

| |Amountsm EUR|Times¹|
|minimum|maximum|base|threshold|
|--|------------|------|
|-------|-------|----|---------|
|Purchases|0.01|99,999.99|3 minutes|120 minutes|
|Refunds|–|–|–|–|

**Note:**

1.  The base and threshold times are defined as follows:
    -   *The base time* is the average estimated time between the moment a payment is initiated in the payment platform to the moment the payment result is sent to the web service. The base time evaluation is made on the assumption of normal operation of all technical facilities and communication channels and typical customer behaviour. Use the base time to estimate when to react to the absence of payment result callbacks or when to check payment status \([details](en_Gate_payment_status_request.md#)\).
    -   *The threshold time* is the maximum possible time between the moment a payment is initiated in the payment platform to the moment the web service receives the callback with the payment result. A payment is automatically assigned the `decline` status if it wasn't processed within the threshold time. For individual customisation of the threshold time limit, contact Ecommpay technical support.

### Processing scenarios {#section_fgt_sdl_ggb .section}

To perform a purchase by using the Satispay method, you need to redirect the customer to the Satispay service, while to make a refund, you need to receive a request from the customer and notify the customer about the result of the refund via the web service.

![](images/pm/en_satispay_interfaces_pp.svg "Purchase by using Payment Page")

![](images/pm/en_satispay_interfaces_gate.svg "Purchase by using Gate")

![](images/pm/en_pm_satispay_interfaces_gate_refund.svg "Refund by using Gate")

Scenarios for performing operations via the main interfaces of the payment platform correspond to those presented in the diagrams. Similarly, when additional features \(such as payment links\) are used, scenarios for performing operations also correspond to the specifics of those features.

## Purchases by using Payment Page {#en_pm_satispay_pp_purchase}

### General information {#section_gtg_vxk_m2b .section}

To process a purchase through Payment Pageby using the Satispay method, the merchant's web service is required to send a request with all required parameters and signature to the Ecommpay URL and receive a callback with the result.The full sequence and special aspects of purchase processing are provided below.

![](images/pm/en_satispay_uml_pp.svg)

1.  A customer initiates a purchase in the web service.
2.  The web service sends the request for opening Payment Page to the specified Ecommpay URL.
3.  The request for opening Payment Page is sent to the payment platform.
4.  The payment platform receives the request and validates the required parameters and signature.
5.  Payment Page is generated based on the project and request parameters.
6.  Payment Page is displayed to the customer.
7.  The customer selects the Satispay method.
8.  The payment platform receives the request for processing the payment by using the Satispay method.
9.  The payment platform processes the request and sends it to the Satispay service.
10. The request is processed on the Satispay service side.
11. The data for redirecting the customer to the Satispay service is sent from the Satispay service to the payment platform.
12. The data for redirecting the customer is sent from the payment platform to Payment Page.
13. The customer is redirected to the Satispay service.
14. The customer completes all required payment steps.
15. The purchase is processed in the Satispay service.
16. The result information is displayed to the customer in the Satispay service.
17. The customer is redirected to Payment Page.
18. The Satispay service sends a notification about the result to the payment platform.
19. The payment platform sends the payment result callback to the web service.
20. The payment platform sends the result information to Payment Page.
21. The result information is displayed to the customer on Payment Page.

Information about the formats of requests and callbacks used for processing payments by using the Satispay method via Payment Page is presented further in this section; general information about working with the Payment Page API is presented in [Interaction concepts](en_pp_interaction_organisation.md#).

### Request format {#section_p5j_fgl_ggb .section}

There are several things you need to consider when sending purchase requests by using the Satispay method:

1.  The following parameters required for any payment must be specified:
    -   `project_id`—project identifier obtained from Ecommpay during integration
    -   `payment_id`—payment identifier unique within the project
    -   `payment_currency`—payment currency code in the ISO-4217 alpha-3 format
    -   `payment_amount`—payment amount in the smallest currency unit
    -   `customer_id`—customer identifier unique within the project
2.  Additionally, it is recommended to specify the first, last names, as well as the country code of the customer in the parameters `customer_first_name`, `customer_last_name` and `customer_country`. To avoid errors during payment processing it is recommended to set the value length of 3 to 100 characters in the parameters `customer_first_name` and `customer_last_name`. If any of these parameters are missing, the payment form may display input fields for entering the missing values \(details are available in [Submission of additional payment information](en_pp_clarification.md)\).
3.  If you need to have the payment form displayed with the Satispay method selected, set the `force_payment_method` parameter to `satispay`.
4.  Additionally, any other parameters available for working with Payment Page can be used \([details](en_PP_Parameters.md)\).
5.  After all target parameters are specified, generate a signature \([details](en_platform_signature.md#)\).

Thus, a correct request for opening the payment form using the Satispay method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), customer information, and signature, as well as possible additional parameters.

``` {#codeblock_gdb_pts_w2c .language-json}
{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 1000,
   "payment_currency": "EUR",
   "customer_id": "customer1",
   "customer_first_name": "John",
   "customer_last_name": "Doe",
   "customer_country": "IT",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}
```

``` {#codeblock_y4m_sqb_y2c .language-json}
{
   "project_id": 120,
   "payment_id": "580",
   "payment_amount": 1000,
   "payment_currency": "EUR",
   "customer_id": "customer1",
   "customer_first_name": "John",
   "customer_last_name": "Doe",
   "customer_country": "IT",
   "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg=="
}
```

### Callback format {#section_dpx_2hl_ggb .section}

The Satispay method uses the standard format for callbacks to deliver purchase results. For more information, see [Handling callbacks](en_platform_callbacks.md#).

The following is the example of a callback with information about a `10.00 EUR` purchase made in the `133661` project.

``` {#codeblock_hdb_pts_w2c .language-json}
{
        "customer": {
            "id": "1"
        },
        "project_id": 133661,
        "payment": {
            "id": "TEST_PAYMENT_362502",
            "type": "purchase",
            "status": "success",
            "date": "2025-04-04T14:55:28+0000",
            "method": "Satispay",
            "sum": {
                "amount": 1000,
                "currency": "EUR"
            },
            "description": "PAYMENT_362502"
        },
        "operation": {
            "sum_initial": {
                "amount": 1000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 1000,
                "currency": "EUR"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 16591,
                "payment_id": "140346607697",
                "auth_code": ""
            },
            "id": 257010170581,
            "type": "sale",
            "status": "success",
            "date": "2025-04-04T14:55:28+0000",
            "created_date": "2025-04-04T14:55:08+0000",
            "request_id": "48b4eb2990e744d4f0267b55763daf4fb6ea73776ea111c22-00000258"
        },
        "signature": "0iaViuowAWtp9dN0zL1+RvWrlLD9ThXaaIJI5OtWqp/UayQiqbDh6w=="
    }
}

```

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

``` {#codeblock_idb_pts_w2c .language-json}
{
        "customer": {
            "id": "1"
        },
        "project_id": 133661,
        "payment": {
            "id": "TEST_PAYMENT_155297",
            "type": "purchase",
            "status": "decline",
            "date": "2025-04-04T15:39:41+0000",
            "method": "Satispay",
            "sum": {
                "amount": 1000,
                "currency": "EUR"
            },
            "description": "PAYMENT_155297"
        },
        "operation": {
            "sum_initial": {
                "amount": 1000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 1000,
                "currency": "EUR"
            },
            "code": "20000",
            "message": "General decline",
            "provider": {
                "id": 16591,
                "payment_id": "",
                "auth_code": ""
            },
            "id": 25690010171161,
            "type": "sale",
            "status": "decline",
            "date": "2025-04-04T15:39:41+0000",
            "created_date": "2025-04-04T15:39:40+0000",
            "request_id": "762937223da5db339a4f69ffe5e63f9d6bfc97566222a88-00025691"
        },
        "signature": "VCcJEPV5gbzBoF69NRYa/eoE9DaRlXOpm8S/HhTXFHZzPmoo24jYg=="
    }
}

```

### Useful links {#section_xpz_thl_ggb .section}

The following articles can be useful when implementing purchases via Payment Page:

-   [Interaction concepts](en_pp_interaction_organisation.md#)—about the interaction with the payment platform by using Payment Page.
-   [Signature generation and verification](en_platform_signature.md#)—about the procedure of generating and verifying signatures in requests and callbacks.
-   [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations.
-   [One-time one-step purchase](en_platform_sms_model.md)—about processing of one-time one-step purchases with immediate debiting of funds by using Payment Page.
-   [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations.

## Purchases by using Gate {#en_pm_satispay_gate_purchase}

### General information {#section_lsx_3jl_ggb .section}

To process a purchase through Gate by using the Satispay method, the merchant's web service is required to do the following:

1.  Send a request with all the required parameters and signature to the Ecommpay URL.
2.  Receive an intermediate callback from the payment platform and redirect the customer to the Satispay service.
3.  Receive the final callback from the payment platform.

The full sequence and special aspects of purchase processing are provided below.

![](images/pm/en_satispay_uml_gate.svg)

1.  A customer initiates a purchase by using the Satispay method in the web service.
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.
4.  The payment platform validates the required parameters and signature in the request.
5.  The payment platform sends the response to the web service with information about the receipt of the request and its validity \([details](en_gate_interaction_organisation.md#)\).
6.  The payment platform performs further processing of the request \(with parameter consistency check\) and sends it to the Satispay service.
7.  The request is processed on the Satispay service side.
8.  The Satispay service sends the redirection data to the payment platform.
9.  The payment platform sends the callback with the redirection data to the web service.
10. The customer is redirected to the Satispay service.
11. The customer completes all required payment steps.
12. The purchase is processed in the Satispay service.
13. The result is displayed to the customer.
14. The customer is redirected to the web service.
15. The Satispay service sends the payment result notification to the payment platform.
16. The payment platform sends the payment result callback to the web service.
17. The customer receives the payment result information from the web service.

Information about the formats of requests and callbacks used for processing payments by using the Satispay method via Gate is presented further in this section. General information about working with the Gate API is presented in [Interaction concepts](en_gate_interaction_organisation.md#).

### Request format {#section_osx_3jl_ggb .section}

There are several things you need to consider when sending purchase requests by using the Satispay method:

1.  To initiate each purchase, send a separate POST request to the `/v2/payment/wallet/satispay/sale` endpoint. This endpoint belongs to the group [/v2/payment/wallet/\{payment\_method\}/sale](https://api-developers.ecommpay.com/api-specification/wallet/post-v2-payment-wallet-payment-method-sale).
2.  Each request must include the following objects and parameters:
    -   Object `general`—general purchase information:
        -   `project_id`—project identifierobtained from Ecommpay during integration
        -   `payment_id`—payment identifierunique within the project
        -   `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md#)\)
    -   Object `payment`—payment information:
        -   `amount`—payment amount in the smallest currency unit
        -   `currency`—payment currency codein the ISO-4217 alpha-3 format
    -   Object `customer`—customer information:
        -   `id`—customer identifierunique within the project
        -   `ip_address`—customer IP addressrelevant for the initiated payment
3.  Additionally, it is recommended to specify the following objects and parameters:

    -   Object `customer`—customer information:
        -   `first_name`— customer first name \(to avoid errors during payment processing it is recommended to set the following value length—from 3 to 100 characters\)
        -   `last_name`—customer last name \(to avoid errors during payment processing it is recommended to set the following value length—from 3 to 100 characters\)
        -   `country`—customer country code in accordance with ISO 3166-1 alpha-2
    If any of these parameters are missing, the payment platform may send the list of missing parameters in a callback requesting additional information submission \(details are available in [Submission of additional payment information](en_Gate_Clarification.md)\).

4.  Additionally, any other parameters included in the specification can be used.

Thus, a correct purchase request by using the Satispay method must contain the project identifier, basic payment information \(identifier, amount, and currency code\), customer information, and signature, as well as possible additional parameters.

``` {#codeblock_wwl_c5s_w2c .language-json}
{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 1000,
    "currency": "EUR"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0",
    "first_name": "John",
    "last_name": "Johnson",
    "country": "IT"
  }
}
```

``` {#codeblock_yzh_brb_y2c .language-json}
{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "amount": 1000,
    "currency": "EUR"
  },
  "customer": {
    "id": "customer123",
    "ip_address": "192.0.2.0",
    "first_name": "John",
    "last_name": "Johnson",
    "country": "IT"
  }
}
```

### Formats of intermediate callbacks for customer redirection {#section_nxg_hmn_zgb .section}

Each payment made with the Satispay method requires redirection of customers from the merchant's web service to the Satispay service. To redirect a customer it is necessary to receive an intermediate callback from the payment platform and use the information included in the `redirect_data` object. The format of such callbacks is standard \([details](en_platform_callbacks.md#)\), and the following objects and parameters are included in the `redirect_data` object:

-   `body`—object with data to be sent in the request body
-   `method`—parameter specifying the HTTP method for sending the request \(`GET` or `POST`\)
-   `url`—parameter containing a link for redirection

``` {#codeblock_rlf_tpb_y2c .language-json}
  "redirect_data": {
    "body": {},
    "method": "GET",
    "url": "https://www.example.com/pay"
  }
```

### Final callback format {#section_dpx_2hl_ggb .section}

The Satispay method uses the standard format for callbacks to deliver purchase results. For more information, see [Handling callbacks](en_platform_callbacks.md#).

The following is the example of a callback with information about a `10.00 EUR` purchase made in the `133661` project.

``` {#codeblock_hdb_pts_w2c .language-json}
{
        "customer": {
            "id": "1"
        },
        "project_id": 133661,
        "payment": {
            "id": "TEST_PAYMENT_362502",
            "type": "purchase",
            "status": "success",
            "date": "2025-04-04T14:55:28+0000",
            "method": "Satispay",
            "sum": {
                "amount": 1000,
                "currency": "EUR"
            },
            "description": "PAYMENT_362502"
        },
        "operation": {
            "sum_initial": {
                "amount": 1000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 1000,
                "currency": "EUR"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 16591,
                "payment_id": "140346607697",
                "auth_code": ""
            },
            "id": 257010170581,
            "type": "sale",
            "status": "success",
            "date": "2025-04-04T14:55:28+0000",
            "created_date": "2025-04-04T14:55:08+0000",
            "request_id": "48b4eb2990e744d4f0267b55763daf4fb6ea73776ea111c22-00000258"
        },
        "signature": "0iaViuowAWtp9dN0zL1+RvWrlLD9ThXaaIJI5OtWqp/UayQiqbDh6w=="
    }
}

```

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

``` {#codeblock_idb_pts_w2c .language-json}
{
        "customer": {
            "id": "1"
        },
        "project_id": 133661,
        "payment": {
            "id": "TEST_PAYMENT_155297",
            "type": "purchase",
            "status": "decline",
            "date": "2025-04-04T15:39:41+0000",
            "method": "Satispay",
            "sum": {
                "amount": 1000,
                "currency": "EUR"
            },
            "description": "PAYMENT_155297"
        },
        "operation": {
            "sum_initial": {
                "amount": 1000,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 1000,
                "currency": "EUR"
            },
            "code": "20000",
            "message": "General decline",
            "provider": {
                "id": 16591,
                "payment_id": "",
                "auth_code": ""
            },
            "id": 25690010171161,
            "type": "sale",
            "status": "decline",
            "date": "2025-04-04T15:39:41+0000",
            "created_date": "2025-04-04T15:39:40+0000",
            "request_id": "762937223da5db339a4f69ffe5e63f9d6bfc97566222a88-00025691"
        },
        "signature": "VCcJEPV5gbzBoF69NRYa/eoE9DaRlXOpm8S/HhTXFHZzPmoo24jYg=="
    }
}

```

### Useful links {#section_xsx_3jl_ggb .section}

The following articles can be useful when implementing purchases via Gate:

-   [Interaction concepts](en_gate_interaction_organisation.md#)—about the interaction with the payment platform by using Gate.
-   [Signature generation and verification](en_platform_signature.md#)—about the procedure of generating and verifying signatures in requests and callbacks.
-   [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations.
-   [One-time one-step purchase](en_platform_sms_model.md)—about processing of one-time one-step purchases with immediate debiting of funds by using Gate.
-   [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations.

## Refunds by using Gate {#en_pm_satispay_gate_refund}

### General information {#section_lsx_3jl_ggb .section}

To perform a refund through Gate by using the Satispay method, send a request with all required parameters and signature to the Ecommpay URL and receive a callback with the result.The full sequence and special aspects of refund performing are provided below.

![](images/pm/en_pm_satispay_uml_gate_refund.svg)

1.  A customer initiates a refund.
2.  The web service sends the request for performing the refund by using Gate to the specified Ecommpay URL.
3.  The payment platform receives the request.
4.  The payment platform validates the required parameters and signature in the request.
5.  The payment platform sends the response to the web service with information about the receipt of the request and its validity \([details](en_gate_interaction_organisation.md#)\).
6.  The payment platform performs further processing of the request \(with parameter consistency check\) and sends it to the Satispay service.
7.  The refund is processed on the side of the Satispay service.
8.  The Satispay service sends the result notification to the payment platform.
9.  The payment platform sends the result callback to the web service.
10. The customer receives the refund result information from the web service.

Information about the formats of requests and callbacks used for performing refunds by using the Satispay method via Gate is presented further in this section. General information about working with the Gate API is presented in [Interaction concepts](en_gate_interaction_organisation.md#).

### Request format {#section_osx_3jl_ggb .section}

There are several things you need to consider when sending refund requests by using the Satispay method:

1.  To initiate each refund, send a separate POST request to the [/v2/payment/refund](https://api-developers.ecommpay.com/api-specification/direct-debit/post-v2-payment-refund) endpoint.
2.  Each request must include the following objects and parameters:
    -   Object `general`—general refund information:
        -   `project_id`—project identifierobtained from Ecommpay during integration
        -   `payment_id`—identifier of the payment that needs to be refunded
        -   `signature`—request signaturegenerated after all required parameters are specified \(details—in the [Signature generation and verification](en_platform_signature.md#)\)
    -   Object `payment`—refund information:
        -   `description`—refund description or comment
        -   `amount`—refund amount in the smallest currency unit \(required for a partial refund\)
        -   `currency`—refund currency codein the ISO-4217 alpha-3 format \(required for a partial refund\)
    -   Object `customer`—customer information:
        -   `ip_address`—customer IP addressrelevant for the initiated refund
3.  Additionally, any other parameters included in the specification can be used.

Thus, a correct refund request by using the Satispay method must contain the project and payment identifiers, description of the refund, the customer IP address, signature, and, if necessary, currency code and refund amount.

``` {#codeblock_fqj_w1d_t2c .language-json}
{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "description": "test refund",
    "amount": 1000,
    "currency": "EUR"
  },
  "customer": {
    "ip_address": "192.0.2.0"
  }
}
```

``` {#codeblock_bxk_glb_y2c .language-json}
{
  "general": {
    "project_id": 210,
    "payment_id": "test_payment",
    "signature": "PJkV8ej\/UG0Di8hTng6JvipTv+AWoXW\/9MTO8yJA=="
  },
  "payment": {
    "description": "test refund",
    "amount": 1000,
    "currency": "EUR"
  },
  "customer": {
    "ip_address": "192.0.2.0"
  }
}
```

### Callback format {#section_dpx_2hl_ggb .section}

The Satispay method uses the standard format for callbacks to deliver refund results. For more information, see [Handling callbacks](en_platform_callbacks.md#).

The following is the example of a callback with information about a `5.00 EUR` partial refund made in the `433772` project.

``` {#codeblock_pmy_w1d_t2c .language-json}
{
        "project_id": 433772,
        "payment": {
            "id": "TEST_PAYMENT_122468",
            "type": "purchase",
            "status": "partially refunded",
            "date": "2024-12-18T14:36:34+0000",
            "method": "Satispay",
            "sum": {
                "amount": 500,
                "currency": "EUR"
            },
            "description": "TEST_PAYMENT_122468"
        },
        "customer": {
            "id": "1",
            "phone": "*************"
        },
        "operation": {
            "id": 3997000012221,
            "type": "refund",
            "status": "success",
            "date": "2024-12-18T14:36:34+0000",
            "created_date": "2024-12-18T14:36:30+0000",
            "request_id": "de99efb8e28702b165b5f9f117-00003998",
            "sum_initial": {
                "amount": 500,
                "currency": "EUR"
            },
            "sum_converted": {
                "amount": 500,
                "currency": "EUR"
            },
            "code": "0",
            "message": "Success",
            "provider": {
                "id": 21414,
                "payment_id": "1418092071",
                "auth_code": ""
            }
        },
        "signature": "rq3TC04YQt1WFgSociHhJyfvjIQsj7n67UQ=="
    }
```

The following is the example of a callback with information about a declined refund.

``` {#codeblock_iqj_w1d_t2c .language-json}
 {
    "project_id": 433772,
    "payment": {
        "id": "TEST_PAYMENT_122468",
        "type": "purchase",
        "status": "partially refunded",
        "date": "2024-12-18T14:36:34+0000",
        "method": "Satispay",
        "sum": {
            "amount": 500,
            "currency": "EUR"
        },
        "description": "TEST_PAYMENT_122468"
    },
    "customer": {
        "id": "1",
        "phone": "*************"
    },
    "operation": {
        "id": 3997000012956,
        "type": "refund",
        "status": "decline",
        "date": "2024-12-22T14:22:44+0000",
        "created_date": "2024-12-22T14:22:44+0000",
        "request_id": "b3de84c717d1ba574598a637f856a-00002267",
        "sum_initial": {
            "amount": 5000,
            "currency": "EUR"
        },
        "sum_converted": {
            "amount": 5000,
            "currency": "EUR"
        },
        "code": "3283",
        "message": "Refund amount more than init amount",
        "provider": {
            "id": 21414,
            "payment_id": "1418092071",
            "auth_code": ""
        }
    },
    "signature": "PWoXcLWZbWyySxLSpFq3TC04YQt1WFgSocteIUw=="
}
```

### Useful links {#section_xsx_3jl_ggb .section}

The following articles can be useful when implementing refunds via Gate:

-   [Interaction concepts](en_gate_interaction_organisation.md#)—about the interaction with the payment platform by using Gate.
-   [Signature generation and verification](en_platform_signature.md#)—about the procedure of generating and verifying signatures in requests and callbacks.
-   [Payment processing](en_platform_payment_model.md)—about the types, processing models, and possible statuses of supported payments and operations.
-   [Purchase refunds](en_Gate_Refund.md)—about performing of refunds by using Gate.
-   [Handling operation processing information](en_platform_payment_info_codes.md)—about error and response codes that are used in the payment platform to record information about performing of operations.

## Refunds by using Dashboard {#en_pm_dash_refund}

When working with Dashboard, you can perform *single* and *mass* refundsby using the Satispay method.

-   To perform a single refund, select the target purchase, open its information tab, specify the amount of the refund, send a request and verify that the refund has been performed.
-   To perform a mass refund, prepare and upload a file with information about all target refunds, send a batch request, and verify that the refunds have been performed.

    Use a CSV file structured according to the requirements presented in the [Mass payments data](en_dbl_payments.md#) section. The refund parameters must comply with the [requirements](pm_satispay.md#) \(you do not have to generate a signature because it is specified by Dashboard\).


More informationabout performing refunds by using Dashboard is presented in a [separate section](en_dbl_payments.md#).

## Analysis of payments results {#en_pm_satispay_dash_analysis}

To analyse information about payments made with the Satispay method and other methods, you can use:

-   Dashboardinterface toolkitwith various lists and analytic panels.
-   Reports in CSV file format, available via the **Reports** section \(one-time and periodically\).
-   Data in JSON format, sent by program requests to a specified URL by using the Data API interface.

If you have any questions, refer to the documentation \([Dashboard](en_dbl_about.md) and [Using Data API](en_dbl_api_protocol.md)\) and Ecommpay technical support.