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

Was this helpful?

  1. Integration Guide
  2. Payment Methods & Wallets

Alipay+

PreviousAccount-to-Account PaymentsNextApple Pay

Last updated 4 months ago

Was this helpful?

Alipay is now Alipay+.

To migrate from Alipay to Alipay+, an additional agreement must be signed. Please contact your account manager or our

Alipay+ transactions can be processed via the Saferpay JSON API. However, as Alipay+ is a third party provider, there are a few things to consider.

General requirements

The handling of Alipay+ payments with Saferpay requires:

  • A and thus a valid identification with a username and password for the Saferpay system.

  • At least one active Saferpay terminal on which the payment can be carried out. This could be a Saferpay Payment Page or a Saferpay Secure PayGate terminal.

  • A valid Alipay contract.

For Alipay+ activation on the Saferpay terminal, please contact our

Technical requirements

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

  • JSON API Version 1.11 or later

  • Refund:

    • A refund has always the status CAPTURED and thusly cannot be cancelled. Make sure that you really want to execute it. Furthermore, in order to execute a refund, the turnover on this day must be greater than or equal to the amount to be refunded. The refunded amount won't be taken from your bank account, instead it will be subtracted from the overall turnover since the last batch close.

    • Note that the CaptureId, needed for a refund, is returned as part of the response of .

  • The parameter OrderId is limited to 50 characters.

  • The notification URLs, inside theNotification conatiner are mandatory, in order to avoid missing payment successes. See the for further information.

Supported features

Feature

Support

Capture/Cancel

❌/❌

Multipart Captures

❌

Secure Card Data

❌

✅

Recurring Payments

❌

3D Secure

❌

Dynamic Currency Conversion (DCC)

❌

Mail Phone Order

❌

✅

✅

Testing

Please refer to , if you want to test Alipay+.

Refunds
Omni-Channel
Needs attention!
Testing
corresponding license
Payment Page
Payment Page Assert
this chapter
customer service
customer service
Payment Page process