LogoLogo
BlogLogin
English
English
  • An Introduction to Saferpay
    • Licensing
      • Legacy licensing
    • Reconciliation
    • Acquirers & Payment Methods
    • Web Shop Plugins and certified partners
      • ePages Beyond
      • ePages NOW
      • Magento 2
      • Odoo
      • PrestaShop
        • PrestaShop User Guide
      • Salesforce Commerce Cloud
      • SAP Commerce Cloud
      • Shopware 6
        • Shopware 6 User Guide - German
        • Shopware 6 User Guide - English
      • WordPress WooCommerce
      • Shopify
    • Supported Languages
    • Common Saferpay terms - Glossary
  • News
    • Changes for transactions without customer presence
    • Changes for the Saferpay Hosted Forms, Fields and Payment Page
  • Quick Links
    • Web Shop Plugins and certified partners
    • Secure PayGate
    • User Administration
    • Payment Page Configuration
    • Risk Management
    • API Authentication
  • Interfaces
    • Payment API (aka JSON API)
    • Management API
    • Backoffice
      • The Home screen
      • Batch Processing
      • Transactions
        • Transaction Details
        • Batch Close
        • Declined transactions
        • Pending authorizations
        • Analytics
        • SEPA Refunds Export
        • Authorization & Payment
        • Credit
      • Risk Management
      • Secure PayGate / Payment Links
      • Secure Card Data
        • Secure Card Data Details
      • Settings
        • JSON API basic/Client Certificate authentication
        • User Administration
        • Payment Page Configuration
      • Online Support
      • User Profile
    • Saferpay OnSite
    • Feedback
  • Integration Guide
    • Integrating Saferpay
    • Ways of integration
      • General Information
        • Data Security and PCI DSS
        • Versioning
        • 3-D Secure
        • PSD2
        • Dynamic Currency Conversion
        • Iframe Integration and CSS
        • Fraud Intelligence
          • Silver
          • Fraud Intelligence Integration
      • Payment Page
        • Payment Page checklist
      • Transaction Interface
        • Recurring Payments
        • Refunds
          • SEPA Refunds
      • Capture and Daily Closing
        • Partial Captures
          • Marketplace
      • Secure Card Data - Tokenization
      • Saferpay Fields
      • Inquire Interfaces
      • Mobile Integration
      • Omni-Channel
      • Mail Phone Order
      • Error Handling
      • API Health Check
      • Saferpay API Specification
    • Payment Methods & Wallets
      • General and special cases
      • Account-to-Account Payments
      • Alipay+
      • Apple Pay
      • American Express
      • Bancontact
      • Billie
      • blik
      • Click to Pay
      • Diners Club International & Discover Card
      • eps
      • giropay
      • Google Pay
      • iDEAL 2.0
      • JCB
      • Klarna Payments
      • Maestro International
      • Mastercard
      • paydirekt
      • PayPal
      • PostFinance Pay
      • Przelewy24
      • Reka
      • SEPA Direct Debit
      • Sofort by Klarna
      • TWINT
      • UnionPay
      • Visa & V PAY
      • WeChat Pay
      • WL Crypto Payments
    • Testing
    • Go-Live
    • Frequently Asked Questions
    • Saferpay Demo
      • Saferpay Demo Environment
      • Saferpay Demo Shop
    • Support
    • Changelog
Powered by GitBook
On this page
  • General requirements
  • Technical requirements
  • Supported features
  • Handling Refunds
  • Querying the transaction status via API
  • Testing

Was this helpful?

  1. Integration Guide
  2. Payment Methods & Wallets

WL Crypto Payments

PreviousWeChat PayNextTesting

Last updated 4 months ago

Was this helpful?

Saferpay also offers the possibility to pay via the Bitcoin and Etherum crypto currencies. The following chapter will cover the activation and integration of this payment method.

General requirements

The handling of Crypto currencies with Saferpay requires:

  • A 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.

  • In general, the payout of transactions made via cryptocurrencies will happen in CHF or EUR. However, payments in EUR are currently only possible in Belgium and Luxembourg. Any other currency, or payout to a cryptocurrency wallet, is not supported!

For WL Crypto Payments activation on the Saferpay terminal and the necessary contract, please contact your Saferpay sales contact.

Technical requirements

The general integration of Crypto Payments can only be done via the and requires the following things to be noted:

  • API SpecVersion 1.22+

  • The parameter OrderId is limited to 50 characters.

Supported features

Feature

Support

Capture/Cancel

❌

Multipart Captures

❌

Secure Card Data

❌

Refunds

✅

Recurring Payments

❌

3D Secure

❌

Dynamic Currency Conversion (DCC)

❌

Mail Phone Order

❌

✅

Omni-Channel

❌

Handling Refunds

Refunds are a challenge, as the Blockchain itself does not support them. To circumvent this issue, Bitcoin Swiss offers a process to handle refunds, via a different way.

If a refund is requested, Saferpay will forward this request to Bitcoin Swiss, which will then contact the payer, using the e-mail, which must be provided during the payment. The refund is then processed as a normal bank-transfer and not via the crypto currency.

Due to the fact, that this process takes time, every refund will first have the status PENDING, which will remain, until the refund has been processed correctly.

Once done, Saferpay will recieve a notification and change the status of the refund to CAPTURED.

Querying the transaction status via API

Remember to reference the refund, not the original transaction, that has been refunded!

Testing

Refunds are generally executed normally, via the (or the ), as you would expect. However, while normal refunds either report an AUTHORIZED or CAPTURED status, WL Crypto Payments introduces a thrird status: PENDING.

To automatize this process, you first need to set the PendingNotification.NotifyUrl option, available for the . Once Saferpay recieves a status-update, the NotifyUrl will be called, enabling you to query the final status of the Refund.

The status of a WL Crypto Payments refund can be queried with the JSON API. The corresponding function is the .

This process is basically the same, as with the and follow the same rules.

Please refer to , if you want to test WL Crypto Payments.

corresponding license
Payment Page
Transaction/Refund
Inquire Interface
Needs attention!
Testing
Backoffice
Saferpay API
Notification URLs, within the Payment Page process
this chapter