Hosted Checkout Page

Understand 3-D Secure statuses

To help you keep track of your transactions and their 3-D Secure status, it is important to differentiate between a transactions': 

• 3-D Secure status: The result of the authentication check provided by your customer’s issuer. We return this result in property paymentOutput.cardPaymentMethodSpecificOutput.threeDSecureResults.eci in GetPayment/GetPaymentDetails requests
• Global transaction status: The result of the authorisation request provided by your acquirer for the gross amount (as defined in your CreatePayment/CreateHostedCheckout request in property order.amountOfMoney.amount). We return this result in property statusOutput.statusCode. Learn more about the global transaction status and all possible outcomes

The table below gives you a full overview of possible scenarios and how our platform displays them to you:

Integration steps

At one point during the checkout process, you send your customers to our secure payment page. They enter their card details, we send them to your acquirer and provide you with the result.

Check out how the full transaction flow works and what you need to do in each step.

Target endpoint URLs in test / live

Our platform allows you to send requests either to our Test environment or Live environment:

• Endpoint URL TEST: MERCHANT_ID/hostedcheckouts
• Endpoint URL LIVE: MERCHANT_ID/hostedcheckouts

If you are using our Server SDKs, your application will automatically target the respective environment / integration mode URL via instances of CommunicatorConfiguration / IClient / CreateHostedCheckoutRequest. Detailed information about how you can achieve this are available in the next chapter, including full code samples.

Understand payment flow

Our Server SDKs come with a HostedCheckoutAPI. It includes all the methods you need to perform all the steps of a typical payment flow:

1. Your customers go to your check-out page and finalises the purchase
2. You send a CreateHostedCheckout request to us. Use the following code sample for the request:

1. Our platform sends a response in the instance of CreateHostedCheckoutResponse you created upon your request. It contains a partialRedirectionURL property

   // Properties of createHostedCheckoutResponse
   {
       "RETURNMAC": "12345678-90ab-cdef-1234-567890abcdef",
       "hostedCheckoutId": "123456",
       "merchantReference": "7e21badb48fe45848bbc1efef2a88504",
       "partialRedirectUrl": "hostedcheckout/PaymentMethods/Selection/e61340e579e04172a740676ffdda162e"
       "redirectUrl": "https://payment.hostedcheckout/PaymentMethods/Selection/e61340e579e04172a740676ffdda162e"
   }
   

2. You redirect the customers in the browser using the formula https://payment. + PartialRedirectUrl or use the full path from property redirectUrl
   
   Construct this URL using the CreateHostedCheckoutResponse object
   
   The customer enter their card number in the payment mask on the PartialRedirectUrl / redirectUrl and confirm the payment
   
   4'. (Optional): We perform a Fraud check

1. We redirect the customer to her/his issuing bank for 3-D Secure authentication. The cardholder identifies herself/himself

1. Our system receives the result from the issuer. Based on the result, two scenarios are possible:
   
   • If the identification was unsuccessful, we redirect your customers to your ReturnUrl, ending the flow. You request the transaction result as described in step 9)
   • If the identification was successful, the flow continues at step 7
2. We submit the actual financial transaction to the acquirer to process it. We receive the transaction result
   
   
3. We redirect your customers to your ReturnUrl
   
   
4. You request the transaction result from our platform. Use an instance of GetHostedCheckoutResponse and pass the HostedCheckoutId from the response to target the transaction you have just created. From the moment on we have sent a HostedCheckoutId, you can request the result for three hours. After that, our platform deletes the HostedCheckoutId.
   
   

   If your customers have not finished entering their card credentials yet and/or we have not received a final result from your acquirer, property hostedCheckoutStatus.CreatedPaymentOutput.PaymentStatusCategory is null:

   {
     "CreatedPaymentOutput": {},
     "Status": "PAYMENT_CREATED"
   }
   

   
   As soon as we have received a result, this property contains a result that looks like this:

   {
     "CreatedPaymentOutput": {
       "Payment": {
         "HostedCheckoutSpecificOutput": {
           "HostedCheckoutId": "3104703806"
         },
         "Id": "3104703806_0",
         "PaymentOutput": {
           "AmountOfMoney": {
             "Amount": 100,
             "CurrencyCode": "EUR"
           },
         },
         "Status": "CAPTURED",
         "StatusOutput": {
   		.
   		.
   		.
           "StatusCode": 9
         }
       },
       "PaymentStatusCategory": "SUCCESSFUL"
     },
     "Status": "PAYMENT_CREATED"
   }
   

You can also receive the result via webhooks or a PaymentResponse call. Mind that GetPayment accepts a PAYIDSUB instead of a HostedCheckoutId, which is a HostedCheckoutId plus numeric step indicating the PAYIDSUB's order in the transaction's life cycle. "_0" refers to the first step in the transaction life cycle, thus the initial step when creating the transaction:

1. If the transaction was successful, you can deliver the goods / services