Server-to-server
Introduction
Our Server-to-server solution allows you to exchange all transaction-related data between your server and our platform directly. Your customers remain in your webshop environment during the whole payment process, which enables you to
- Define the look and feel of your customers’ journey completely on your own
- Smooth out your customers’ payment experience when using recurring payments or our Hosted Tokenization Page solution
Before you process live transactions, use our test environment. Get to know our solution without costs or any commitments involved! Once you want to go live, check out here how to get a production account or contact us!
Server to server connections require your systems to process card data at some point. This method brings in a very large number of the PCI requirements.
Obtaining a token from our system dramatically via our Hosted Tokenization Page solution reduces the number of your systems that would require assessing as they no longer have card data.
Target most up-to-date API base URL
We encourage you to always target the most up-to-date API base URL when sending requests to our platform. Have a look at our dedicated guides for a full overview:
To allow you a smooth transition, previous API base URLs remain available until further notice.
Get started
To process transactions on our platform with this solution, make sure that
- You have an account on our platform
- At least one of our of our available payment methods is activated in your account. Check in the Back Office via Configuration > Payment methods
- You have configured your API Key and API Secret in your account
- Your server can process server-to-server request via our RESTful API. Using one of our Server SDKs will greatly ease this task
Are you all set? Then learn how to use our Server-to-server in the next chapter!
Integration with Server-to-server
Your customers stay in your webshop environment during the whole payment process. As you send all the data directly to our platform and receive the (intermediate) result in real-time, no other party becomes visible to your customers (except for 3-D Secure challenge flow transactions). This way, you are completely free to design the look and feel of the payment page.
Target endpoint URLs in test / live
Our platform allows you to send requests either to our Test environment or Live environment:
- Endpoint URL TEST: https://payment.preprod.direct.worldline-solutions.com/v2/{merchantId}/payments
- Endpoint URL LIVE: https://payment.direct.worldline-solutions.com/v2/{merchantId}/payments
For transactions with no financial impact, use the TEST-URL. The transactions will be sent to our test environment thereby to your test account
For transactions with a financial impact, use the LIVE-URL. The transactions will be sent to our live environment thereby to your live account
Understand payment flow
Our Server SDKs come with a Payments API. It includes all the methods you need to perform all the steps of a typical payment flow:
- Your customer goes to your check-out page and enters her/his credit card data to finalise the purchase
- You send a CreatePayment request to our to our platform, including the mandatory 3-D Secure properties. A typical request looks like this:
2'(optional). We perform a Fraud check
- Server to server connections require your systems to process card data at some point. This method brings in a very large number of the PCI requirements.
Obtaining a token from our system dramatically via our Hosted Tokenization Page solution reduces the number of your systems that would require assessing as they no longer have card data. -
When processing online transactions, keeping track of your conversion rate is paramount. We are eager to help you with this, via our MyPerformance tool or via our transaction databases our customer support team is happy to share with you.
To ensure we can provide you with the most precise conversion rate data, we highly recommend the following best practices:
- When submitting a transaction request to our platform, always send the customer email address
order.customer.contactDetails.emailAddress - When resubmitting a transaction request to our platform for a unique order (i.e. after having received a
status.statusOutput=2during the first try), always send the sameorder.references.merchantReferencefrom your first try
- When submitting a transaction request to our platform, always send the customer email address
- Our platform sends a response containing a MerchantAction object.
It instructs you how to proceed with the payment. Based on the response, these scenarios are possible:
a) 3-D Secure frictionless flow authentication (MerchantAction.ActionType=null): Your customers use a 3-D Secure enrolled card. The 3-D Secure properties in your CreatePayment request prove to be sufficient for the authentication step. We submit the transaction to the acquirer and provide the result in property StatusOutput.StatusCode. The flow continues at step 9)
b) 3-D Secure challenge flow authentication (MerchantAction.ActionType=REDIRECT): Your customers use a 3-D Secure enrolled card. They need to identify themselves as the rightful card owner. The flow continues at step 4)
c) No 3-D Secure authentication (MerchantAction.ActionType=null): Your customers use a non-3-D Secure enrolled card. We submit the transaction to the acquirer and provide the result in property StatusOutput.StatusCode. The flow continues at step 9)
Find a detailed overview about the implementation of 3-D Secure in our dedicated guide
- You redirect the customers to their issuing bank to the MerchantAction.RedirectData.RedirectURL. Your customers perform the 3-D Secure check
- Our system receives the result from the issuer. Based on the result, two scenarios are possible:
a) If the identification was unsuccessful, we redirect your customers to your ReturnUrl, ending the flow. You can request the transaction result as described in step 8)
b) If the identification was successful, the flow continues at step 6) - We submit the actual financial transaction to the acquirer to process it. We receive the transaction result
- We redirect your customers to your ReturnUrl
- You request the transaction result from our platform via GetPayment or receive the result via webhooks
- If the transaction was successful, you can deliver the goods / services
Use additional possibilities
Our Server-to-server solution offers many more possibilities. Learn here all about its available features.
Replace sensitive data with token
Server to server connections require your systems to process card data at some point. This method brings in a very large number of the PCI requirements.
Obtaining a token from our system dramatically via our Hosted Tokenization Page solution reduces the number of your systems that would require assessing as they no longer have card data.
A token is a credit card profile safely stored on our platform. There are two different types of tokens:
- Permanent tokens for recurring payments
- Temporary tokens for Hosted Tokenization Page transactions
A typical request replacing card data with a permanent/temporary token looks like this: