> For the complete documentation index, see [llms.txt](https://docs.saferpay.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saferpay.com/home/integration-guide/payment-methods/reka.md).

# Reka

Reka payments can be processed with Saferpay without much effort. This chapter describes what needs to be considered in this regard.

## General requirements

The handling of Reka payments with Saferpay requires:

* A [corresponding license ](/home/master/licensing.md)and thus a valid identification with a username and password for the Saferpay system.
* Availability of at least one active Saferpay terminal via which payment can be carried out, and availability of the associated Saferpay TerminalId.
* A valid Reka contract.
  * A corresponding Reka Merchant ID and Terminal ID
* Reka authorizations are valid for 30 days and [must be captured](/home/integration-guide/licences-and-interfaces/capture-and-daily-closing.md) within that time-frame.

### Technical requirements

The general integration of Reka can only be done via the [Payment Page](/home/integration-guide/licences-and-interfaces/payment-page.md) and requires the following things to be noted:

* Spec-Version 1.38, or higher.
  * **Important:** Reka has been backported to SpecVersions 1.38 - 1.44. When implementing Reka for Spec-Versions lower than 1.45, please make sure, that your implementation is capable of processing the new values, returned by the Saferpay API, e.g. PaymentMethods now returning "REKA" as a value, which was previously not specified. 
* **`Payment.OrderId`**: The [OrderId](/home/master/common-saferpay-terms-glossary.md#orderid) is limited to 20 characters.
* **`Payment.PayerNote`**: [Payernote](/home/master/common-saferpay-terms-glossary.md#payernote) is mandatory for Reka payments. If no Payernote is given, Saferpay will automatically take the OrderId -if present-, or the Saferpay transaction ID.
* Multiple refunds are not supported and only one refund can be made per transaction.

Furthermore, for other flows (Refunds etc.), please also refer to the table below.

### Supported features

| Feature                                                                                                                                                                               |    Support   |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------: |
| [Capture](/home/integration-guide/licences-and-interfaces/capture-and-daily-closing.md)/[Cancel](/home/integration-guide/licences-and-interfaces/capture-and-daily-closing.md#cancel) | <p>✅<br></p> |
| Multipart Captures                                                                                                                                                                    |       ❌      |
| Secure Card Data                                                                                                                                                                      |       ❌      |
| [Refunds](/home/integration-guide/licences-and-interfaces/transaction-interface/refunds.md)                                                                                           |       ✅      |
| Recurring Payments                                                                                                                                                                    |       ❌      |
| 3D Secure                                                                                                                                                                             |       ❌      |
| Dynamic Currency Conversion (DCC)                                                                                                                                                     |       ❌      |
| Mail Phone Order                                                                                                                                                                      |       ❌      |
| [Testing](#testing) ([see Activation](#activation))                                                                                                                                   |       ✅      |
| Omni-Channel                                                                                                                                                                          |       ❌      |

## Activation

{% hint style="warning" %}
Please contact your account manager/[our sales](/home/integration-guide/support.md#worldline-sales-team) for Reka activation
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.saferpay.com/home/integration-guide/payment-methods/reka.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.