Novopayment e-commerce FAQ

Worldline Saferpay - Secure Card Data (Save Alias of Card) API

Register the card as an Alias
- during a transaction(within the authorization process) using PaymentPage Initialize -RegisterAlias.
- during a transaction(within the authorization process) using Transaction Interface/Transaction Authorize -RegisterAlias (Compatible with Saferpay Fields Embed)
- using Standalone Registration (Compatible with Saferpay Fields Embed)
Use the Alias (saved card) to do Transactions
- using Transaction Interface/Transaction Initialize (3D Secured)
  1. Add the Alias to PaymentMeans/Alias/Id parameter
  2. Open RedirectUrl in iFrame or Lightbox to do DCC and 3D Secure process
  3. Continue with normal Transaction process flow, Transaction Authorize Get back transaction data & state as response
- using Transaction Interface/Transaction AuthorizeDirect (No 3D Secure, Can be used as Recurring Payment)
  1. Add the alias to PaymentMeans/Alias/Id parameter
  2. Continue with normal Transaction process flow, Process Authorization Results: Transaction data & state as response
Based on transaction data (State, LiabilityShift), your backend decides what to do with the transaction
You either finalize transaction by Capture/Finalize or Cancel/Abort

Good to know

You will need Customer ID, Terminal ID, Fields Access Token, Fields registered URL, Saferpay Fields javascript library URL , (and in case of Payment Page: JSON API username, JSON API password) . You can find and register these from Saferpay Back Office
For test environment, please register your test account here
Your base URL is either https://www.saferpay.com/api OR https://test.saferpay.com/api depending on which environment you are at.
You should store response data in your backend's database while implementing different steps of payment, you would likely need a value from a previous call, e.g. Token from Initialize
It is recommended to build your RedirectNotifyUrls with a unique id of the transaction like this: https://yourshop/notify?id=12345. This way, when this URL is called, you can identify the transaction and find it in your database
Do not mix RedirectUrl, ReturnUrl, RedirectNotifyUrls, and NotifyUrl they are not the same, and serves different purpose. Your IPN is the URL where you get NOTIFIED by your URL being called (via asynchronous _GET). DO NOT IMPLEMENT TRANSACTION STEPS (e.g. CAPTURE) BY RETURN URL, AS YOUR PROCESS CAN BREAK IF CUSTOMER CLOSING BROWSER, LOOSING CONNECTION, ETC.
Always check LiabilityShift results. It is your choice to stand financial responsibility in a possible chargeback of a transaction. We recommend to implement a transaction amount based evaluation e.g. above 10 EUR you drop if LiabilityShift = NO.
Please note in Transaction AuthorizeDirect there is no 3DS on transactions, hence Liability is always on Merchants. This is not a Saferpay thing, this is the Rules and Regulations of the card schemes.
The Transaction is only completed when it's a green dot icon (not circle) in Saferpay Backoffice Interface . Transactions that are not completed (e.g. Authorized state with green circle icon) will release amount automatically back to cardholder's account by time and later charge of the amount might not be possible.