forwardMessage Objekt: /net/dsb/commons/CybersourceAdapter Methode: forwardMessage Version: 1.0.0 Parameter Name Type / LengthOpt. / Mandat.Description requestMessage XML M Cybersource “requestMessage” defined by Cybersource Specification Result Includes the exact request and response XML from Cybersource as well as DSBextensions when a transaction was successful. The result is encapsulated within the standard DSB-Message response. For further information about Cybersource specific XML please refer to the documentation provide by Cybersource. The “authorisation-transaction-guid” is most important element within the XMLfragment “authorisation-result”. This value MUST be given to the order, so that the DSB-systems can associate the result whilst doing the payment processing. Example Request <?xml version=”1.0” encoding=”ISO-8859-1”?> <message version=”1.0” system=”vhs/3”> <header> <client>4711</client> <service-provider>999</service-provider> </header> <body> <requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.28"> <merchantReferenceCode>dsb_user</merchantReferenceCode> <billTo> <firstName>John</firstName> <lastName>Doe</lastName> <street1>1295 Charleston Road</street1> <city>Mountain View</city> ... </billTo> </requestMessage> </body> </message> Example Response <?xml version=”1.0” encoding=”ISO-8859-1”?> <message version=”1.0” system=”vhs/3”> <header> <client>4711</client> <service-provider>999</service-provider> </header> <body> <authorisation-request> <requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.28"> ... </requestMessage> </authorisation-request> <authorisation-result> <c:replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.28"> ... </c:replyMessage> <authorisation-transaction-guid>CA7D-9B27739CDFD3</authorisation-transaction-guid> <date-of-authorisation>20071106</date-of-authorisation> <time-of-authorisation>140529</time-of-authorisation> <authorisation-amount>135.99</authorisation-amount> <authorisation-currency-code>EUR</authorisation-currency-code> </authorisation-result> </body> </message> This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.OKMore information