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 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 within that time-frame.

Technical requirements

The general integration of Reka can only be done via the Payment Page 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 is limited to 20 characters.

• Payment.PayerNote: 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/Cancel	✅
Multipart Captures	❌
Secure Card Data	❌
Refunds	✅
Recurring Payments	❌
3D Secure	❌
Dynamic Currency Conversion (DCC)	❌
Mail Phone Order	❌
Testing (see Activation)	✅
Omni-Channel	❌

Activation

Please contact your account manager/our sales for Reka activation