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
  • Storage in the Secure Card Data Store
  • Stansdalone registration
  • Address collection from PostFinance
  • Testing

Was this helpful?

  1. Integration Guide
  2. Payment Methods & Wallets

PostFinance Pay

PreviousPayPalNextPrzelewy24

Last updated 2 months ago

Was this helpful?

Via the Saferpay JSON API, payments can be handled through PostFinance Pay.

General requirements

Acceptance of PostFinance Pay requires:

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

  • A valid contract with PostFinance.

Technical requirements

The general integration of PostFinance Pay can be done via the and has the following requirements for integration:

  • JSON API Version 1.37 or later.

  • are only available .

  • Postfinance Pay does not support the . .

  • The Payment.OrderId is restricted to a maximum of 18 characters. Anything more will be truncated.

  • The Payment.OrderId is restricted to an alphanumeric format. Special characters (including "-" and "_") will be filtered aut automatically.

PostFinance Pay transactions are only valid for 30 days and must be in this time frame. After 30 days, the reservation will void and the authorized amount can no longer be transferred! However you have a guaranteed payout, within these 30 days.

may only be executed up to 12 months, after the original transaction.

Supported features

Feature

Support

✅ / ✅

✅

✅

3D Secure

❌

Dynamic Currency Conversion (DCC)

❌

Mail Phone Order

❌

✅

Omni-Channel

❌

Storage in the Secure Card Data Store

  • Activation of Saferpay Secure Card Data in the Saferpay merchant account.

  • The feature must also be activated on PostFinance side.

Stansdalone registration

{
  "RegisterAlias": {
    "IdGenerator": "RANDOM_UNIQUE"
  },
  "Type": "POSTFINANCEPAY",
  "LanguageCode": "en",
  "RequestHeader": {
    "SpecVersion": "1.37",
    "CustomerId": "242225",
    "RequestId": "5f543be575b3f3ecff3214257ac6978a",
    "RetryIndicator": 0,
    "ClientInfo": {
      "ShopInfo": "My Shop",
      "OsInfo": "Windows Server 2013"
    }
  },
  "ReturnUrl": {
    "Url": "https://www.myshop.com/"
  }
}

Address collection from PostFinance

This function is currently not yet available and will be delivered at a later date.

Testing

/

✅

✅

If you intend on saving PostFinance Pay-data for later use, Saferpay provides the possibility of storing the payment data inside the Saferpay Secure Card store, for the and the . For this, the following requirements must be met:

If you intend to use the , you need to specify the parameter Type with the value POSTFINANCEPAY, which signals, that you want to save Postfinance Pay payment means.

Please refer to , if you want to test PostFinance Pay.

this chapter
Multipart Captures
Secure Card Data
Refunds
Recurring Payments
Needs attention!
Needs attention!
Testing
corresponding license
Payment Page
Recurring payments
captured
Refunds
Standalone Alias Registration
Capture
via Alias
Cancel
Iframe integration
Saferpay will break out of the IFrame, if necessary
Payment Page
standalone registration