3.35. CRes Redirect

CRes Redirect Parameters

CRes redirect to connecting party’s website is performed when a payer ends Challenge flow. Final redirect is initiated from within payers browser using HTTP POST method. HTTP payload contains CRes parameters which in turn contains base64 encoded json (see example below).

Redirect parameter name	Description
serial-number	Unique number assigned by Solid Payments server to particular request from the Merchant
merchant-order-id	Merchant order id
paynet-order-id	Order id assigned to the order by gate.solidpayments.com

Redirect Request Example

Connecting party receives HTTP POST request base64 encoded CRes parameter similar to below:

cres=ewogICJtZXNzYWdlVHlwZSIgICAgOiAiQ1JlcyIsCiAgIm1lc3NhZ2VWZXJzaW9uIiA6ICIyLjEuMCIsCgogICJ0aHJlZURTU2VydmVyVHJhbnNJRCIgOiAic29tZVRocmVlRFNTZXJ2ZXJUcmFuc0lEIiwKICAiYWNzVHJhbnNJRCIgICAgICAgICAgIDogInNvbWVBY3NUcmFuc0lEIiwKCiAgImNoYWxsZW5nZUNvbXBsZXRpb25JbmQiIDogIlkiLAogICJ0cmFuc1N0YXR1cyIgICAgICAgICAgICA6ICJZIgp9

After decoding cres one will find a json similar to below:

{
  "messageType"    : "CRes",
  "messageVersion" : "2.1.0",

  "threeDSServerTransID" : "someThreeDSServerTransID",
  "acsTransID"           : "someAcsTransID",

  "challengeCompletionInd" : "Y",
  "transStatus"            : "Y"
}