Source
Settlement, reconciliation & API — found from sitemap — Saferpay
Checked for Saferpay on 13 Oct 2026
- Page
- https://docs.saferpay.com/home/master/reconciliation
- Checked
- 13 Oct 2026, 14:00 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:02c2198c6e2a1394f0dacc5b008017257b2a363bcb56eab0501ce897675b4ed1
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Reconciliation third party processors Report an error
“However, Saferpay also connects to other third-party processors, such as PayPal. In these cases, you receive reconciliation data from that processor.”
-
Order id reconciliation Report an error
“The Payment.OrderId, also known as the reference number, plays a vital role in reconciliation. Your system defines this value. Saferpay then routes it to the respective processor.”
-
Order id optional Report an error
“Although optional, we highly recommend using it.”
-
Order id unique recommendation Report an error
“Although not required, we recommend making your Order ID unique.”
-
Reconciliation contact Report an error
“When in doubt, contact your Account Manager. This is usually the person with whom you signed your current contracts.”
2 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- The Compliance Officer Settlement, reconciliation & API
- The E-Commerce Lead Settlement, reconciliation & API
- The Payments Engineer Settlement, reconciliation & API
- The Finance Lead Settlement, reconciliation & API
- The Skeptic Settlement, reconciliation & API
- The SaaS Founder Settlement, reconciliation & API