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
  • The importance of the OrderId
  • Who to contact?

Was this helpful?

  1. An Introduction to Saferpay

Reconciliation

PreviousLegacy licensingNextAcquirers & Payment Methods

Last updated 2 years ago

Was this helpful?

Reconciliation is an important topic for every merchant, especially in terms of accounting. However, it is not always clear, where this data comes from. This chapter aims to clarify some things about this topic.

First and foremost, you need to understand the general structure:

As you can see, Saferpay is not directly involved with your reconciliation. The reconciliation itself is handled by your processor. As a PSP (Payment Service Processor) Saferpay consolidates your processors into one API and forwards the necessary data for reconciliation towards the respective processor.

A processor can be multiple things. For example, Worldline also is a processor -Often also called "Acquirer"- for credit cards. Saferpay may be a part of Worldline, but it is not your processor. You will get your reconciliation from Worldline, but not directly from Saferpay, which is important to distinguish.

The importance of the OrderId

The Payment.OrderId -also known as reference number- plays a vital role within your reconciliation. This value is set/defined by your system and then routed by Saferpay to the respective processor.

The Id will then show up inside your reconciliation-files, so each transaction can then be easily connected to an order.

Thusly, while optional, we highly recommend its usage.

While it is not blocked, we also recommend making your OrderId unique, for obvious reasons.

Who to contact?

So who should you contact, if you have questions about your reconciliation? When in doubt, you should contact your Account Manager. This is usually the person, you have signed your current contracts with.

If you are unsure about who is your SPOC in this case, you should directly contact the sales-team of the respective processor.

However Saferpay also connects towards other -3rd party- processors, for example . In these cases, you would get your reconciliation-data from that specific processor.

For Worldline, you can .

PayPal
find the general contact over here