Difference between revisions of "Authorization relay response"

From PlatiOnline.EU
Jump to: navigation, search
(→‎POST (Direct PlatiOnline Server - Merchant Server) - PlatiOnline Template)
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
 
== Payment Authorization Relay Response ==
 
== Payment Authorization Relay Response ==
  
Line 5: Line 6:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! Response method !! Comments
+
! Response method
 +
! Comments
 
|-
 
|-
−
| '''PTOR''' || POST using JavaScript
+
| '''PTOR'''
 +
| POST using JavaScript
 
|-
 
|-
−
| '''POST_S2S_PO_PAGE''' || POST server PO to merchant server, customer get the PO template
+
| '''POST_S2S_PO_PAGE'''
 +
| POST server PO to merchant server, customer get the PO template
 
|-
 
|-
−
| '''POST_S2S_MT_PAGE''' || POST server PO to merchant server, customer get the Merchant template
+
| POST_S2S_MT_PAGE
 +
| DEPRECATED - POST server PO to merchant server, customer get the Merchant template
 
|-
 
|-
−
| '''SOAP_PO_PAGE''' || POST SOAP server PO to merchant server, customer get the PO template
+
| '''SOAP_PO_PAGE'''
 +
| POST SOAP server PO to merchant server, customer get the PO template
 
|-
 
|-
−
| '''SOAP_MT_PAGE''' || POST SOAP server PO to merchant server, customer get the Merchant template
+
| SOAP_MT_PAGE
 +
| DEPRECATED '''- '''POST SOAP server PO to merchant server, customer get the Merchant template
 
|-
 
|-
−
| '''GET''' || '''DISABLED imposible to use Plati Online 5.x'''
+
| '''GET'''
 +
| '''DISABLED - it is imposible to use it starting Plati Online 5.0'''
 
|}
 
|}
  
 
'''Also merchants can setup a parameter to instruct Plati Online system to send the transaction decline response to the merchant's server.'''
 
'''Also merchants can setup a parameter to instruct Plati Online system to send the transaction decline response to the merchant's server.'''
  
 +
 
  
 
== PlatiOnline Authorization relay response ==
 
== PlatiOnline Authorization relay response ==
−
PlatiOnline Authorization result is automatically sent when acquiring bank accepts or declines amount authorization.
+
 
−
<br />PlatiOnline.ro system provides several methods that allow merchants to receive transaction response:
+
PlatiOnline Authorization result is automatically sent when acquiring bank accepts or declines amount authorization.<br/> PlatiOnline.ro system provides several methods that allow merchants to receive transaction response:
  
 
=== POST (JavaScript PlatiOnline Server - Client Internet Browser - Merchant Server) ===
 
=== POST (JavaScript PlatiOnline Server - Client Internet Browser - Merchant Server) ===
−
This method creates a HTML form where « action » parameter has merchant's URL '''f_relay_response_url'''.
 
−
<br />
 
  
−
* Upon automated '''onLoad''' event, a '''JavaScript''' code will '''« submit » the form'''.
+
This method creates a HTML form where «&nbsp;action&nbsp;» parameter has merchant's URL '''f_relay_response_url'''.
−
* By using this method SESSION variables related to HTTP communication between merchant server and customer's Browser can be used.
+
 
 +
*Upon automated '''onLoad''' event, a '''JavaScript''' code will '''«&nbsp;submit&nbsp;» the form'''.  
 +
*By using this method SESSION variables related to HTTP communication between merchant server and customer's Browser can be used.  
  
 
'''NOTE''': this method is NOT recommended for websites that do not use SSL!
 
'''NOTE''': this method is NOT recommended for websites that do not use SSL!
  
−
<br />'''POST''' QueryString contain '''F_Relay_Message''' and '''F_Crypt_Message''':
+
<br/> '''POST''' QueryString contain '''f_relay_message''' and '''f_crypt_message''':
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! Parameter !! Data type !! Comments
+
! Parameter
 +
! Data type
 +
! Comments
 
|-
 
|-
−
| f_relay_message || text || Authorization XML relay response '''https://secure.plationline.eu/xml_validation/auth.response.v5.xsd''' encrypted with '''AES algorithm'''
+
| f_relay_message
 +
| text
 +
| Authorization XML relay response '''[https://secure.plationline.eu/xml_validation/auth.response.v5.xsd https://secure.plationline.eu/xml_validation/auth.response.v5.xsd]''' encrypted with '''AES algorithm'''
 
|-
 
|-
−
| f_crypt_message || text || '''AES Key''' used to encrypt '''Authorization XML relay response'''
+
| f_crypt_message
 +
| text
 +
| '''AES Key''' (used for encrypting '''Authorization XML relay response''') encrypted with RSA ITSN pair keys
 
|-
 
|-
−
| merchant fields || text || QueryString used on Authorization XML request on tags '''//merchants_fields//PostQueryString''';XML schema '''https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd'''
+
| merchant fields
 +
| text
 +
| QueryString used on Authorization XML request on tags '''//merchants_fields//PostQueryString''';XML schema '''[https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd]'''
 
|}
 
|}
  
 
=== POST (Direct PlatiOnline Server - Merchant Server) - Merchant HTML Page ===
 
=== POST (Direct PlatiOnline Server - Merchant Server) - Merchant HTML Page ===
−
: Using this method allows a direct communication between servers without involving customer's Browser.
 
  
−
* PO Server will POST directly to merchant's URL;
+
:Using this method allows a direct communication between servers without involving customer's Browser.
−
* Merchant server processes transaction result and responds to PO server with a HTML/JavaScript code;
+
 
−
* PO Server saves HTML/JavaScript code and then sends it directly to customer's Browser.
+
*PO Server will POST directly to merchant's URL;  
−
* The customer will view in Browser the merchant generated HTML/JavaScript response.
+
*Merchant server processes transaction result and responds to PO server with a HTML/JavaScript code;  
 +
*PO Server saves HTML/JavaScript code and then sends it directly to customer's Browser.  
 +
*The customer will view in Browser the merchant generated HTML/JavaScript response.  
  
 
'''NOTE''': By using this method, '''SESSION''' variables related to HTTP communication between merchant server and customer's Browser '''CANNOT''' be used on the merchant's server.
 
'''NOTE''': By using this method, '''SESSION''' variables related to HTTP communication between merchant server and customer's Browser '''CANNOT''' be used on the merchant's server.
Line 61: Line 79:
 
'''NOTE''': this method is recommended for websites that do not use SSL!
 
'''NOTE''': this method is recommended for websites that do not use SSL!
  
−
<br />'''POST''' QueryString contain '''F_Relay_Message''' and '''F_Crypt_Message''':
+
<br/> '''SOAP XML''' contain '''f_relay_message''' and '''f_crypt_message''' and merchant's soap tags. Use this schema to validate: '''[http://secure.plationline.eu/xml_validation/auth.soap.response.v5.xsd http://secure.plationline.eu/xml_validation/auth.soap.response.v5.xsd]'''
 +
 
 +
&nbsp;
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! Parameter !! Data type !! Comments
+
! Tag
 +
! Data type
 +
! Comments
 
|-
 
|-
−
| f_relay_message || text || Authorization XML relay response '''https://secure.plationline.eu/xml_validation/auth.response.v5.xsd''' encrypted with '''AES algorithm'''
+
| f_relay_message
 +
| string
 +
| Authorization XML relay response '''[https://secure.plationline.eu/xml_validation/auth.response.v5.xsd https://secure.plationline.eu/xml_validation/auth.response.v5.xsd]''' encrypted with '''AES algorithm'''
 
|-
 
|-
−
| f_crypt_message || text || '''AES Key''' used to encrypt '''Authorization XML relay response'''
+
| f_crypt_message
 +
| text
 +
| '''AES Key''' (used for encrypting '''Authorization XML relay response''') encrypted with RSA ITSN pair keys
 
|-
 
|-
−
| merchant fields || text || QueryString used on Authorization XML request on tags '''//merchants_fields//PostQueryString''';XML schema '''https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd'''
+
| merchant_SoapTags
 +
| complex
 +
| SoapTags used on Authorization XML request on tags '''//merchants_fields//SoapTags''';XML schema '''[https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd]'''
 
|}
 
|}
  
 
=== POST (Direct PlatiOnline Server - Merchant Server) - PlatiOnline Template ===
 
=== POST (Direct PlatiOnline Server - Merchant Server) - PlatiOnline Template ===
−
: It's similar to above method, but customer will view authorization result in a PlatiOnline HTML format.
 
−
: Depending on the transaction result, we provide the following templates:
 
−
* PO Template for '''Authorized transactions''';
 
−
* PO Template for '''Declined transactions'''. In this template we provide a decline message and also allow the customer to retry the transaction by pressing one button;
 
−
* PO Template for '''Pending Verification''' transactions. In this template customer is informed s/he must wait for final transaction result since transaction will undergo a manual verification.
 
−
* PO Template for '''Expired transactions''' (authorized transactions, but completed AFTER the time frame allowed by to merchant for authorization completion has passed - authorization DELTA T) - '''&lt;f_auth_minutes&gt;''' TAG from '''f_message'''
 
  
 +
:It's similar to above method, but customer will view authorization result in a PlatiOnline HTML format.
 +
:Depending on the transaction result, we provide the following templates:
  
−
NOTE: By using this method, SESSION variables related to HTTP communication between merchant server and customer's Browser CANNOT be used on the merchant's server.
+
*PO Template for '''Authorized transactions''';
 +
*PO Template for '''Declined transactions'''. In this template we provide a decline message and also allow the customer to retry the transaction by pressing one button;
 +
*PO Template for '''Pending Verification''' transactions. In this template customer is informed s/he must wait for final transaction result since transaction will undergo a manual verification.
 +
*PO Template for '''Expired transactions''' (authorized transactions, but completed AFTER the time frame allowed by to merchant for authorization completion has passed - authorization DELTA T) - '''<f_auth_minutes>''' TAG from '''f_message'''  
  
 +
'''NOTE''': By using this method, '''SESSION''' variables related to HTTP communication between merchant server and customer's Browser '''CANNOT''' be used on the merchant's server.
  
−
<br />'''POST''' QueryString contain '''F_Relay_Message''' and '''F_Crypt_Message''':
+
'''NOTE''': this method is recommended for websites that do not use SSL!
 +
 
 +
<br/> '''POST''' QueryString contain '''f_relay_message''' and '''f_crypt_message''':
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! Parameter !! Data type !! Comments
+
! Parameter
 +
! Data type
 +
! Comments
 
|-
 
|-
−
| f_relay_message || text || Authorization XML relay response '''https://secure.plationline.eu/xml_validation/auth.response.v5.xsd''' encrypted with '''AES algorithm'''
+
| f_relay_message
 +
| text
 +
| Authorization XML relay response '''[https://secure.plationline.eu/xml_validation/auth.response.v5.xsd https://secure.plationline.eu/xml_validation/auth.response.v5.xsd]''' encrypted with '''AES algorithm'''
 
|-
 
|-
−
| f_crypt_message || text || '''AES Key''' used to encrypt '''Authorization XML relay response'''
+
| f_crypt_message
 +
| text
 +
| '''AES Key''' (used for encrypting '''Authorization XML relay response''') encrypted with RSA ITSN pair keys
 
|-
 
|-
−
| merchant fields || text || QueryString used on Authorization XML request on tags '''//merchants_fields//PostQueryString''';XML schema '''https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd'''
+
| merchant fields
 +
| text
 +
| QueryString used on Authorization XML request on tags '''//merchants_fields//PostQueryString''';XML schema '''[https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd]'''
 
|}
 
|}
  
 
=== GET (Redirect PlatiOnline Server - Client Internet Browser - Merchant Server) ===
 
=== GET (Redirect PlatiOnline Server - Client Internet Browser - Merchant Server) ===
−
: Metoda face un redirect la URL-ul comerciantului cu rezultatul Autorizarii.<br />Utilizand acesta metoda se pot utiliza variabilele '''SESSION''' din comunicarea '''HTTP''' dintre '''serverul comerciantului''' si '''Browserul clientului'''.<br />Lungimea '''QueryString''' este de limitata la 2000 de caractere.<br />Redirectul arata de forma : http(s)://url.comerciant?QueryString
 
  
 +
'''DISABLED'''
 +
 +
=== SOAP (Direct PlatiOnline Server - Merchant Server) - PlatiOnline Template ===
 +
 +
:Using this method allows a direct communication between servers without involving customer's Browser.
 +
:PO Server will post directly to merchant's URL by:
 +
 +
*'''Content-Type="application/soap+xml; charset=utf-8"''';
 +
*'''SOAPAction=RelayResponse''';
 +
 +
:Merchant's server processes transaction result and response to PO Server with a XML code;
 +
 +
*PO Template for '''Authorized transactions''';
 +
*PO Template for '''Declined transactions'''. In this template we provide a decline message and also allow the customer to retry the transaction by pressing one button;
 +
*PO Template for '''Pending Verification''' transactions. In this template customer is informed s/he must wait for final transaction result since transaction will undergo a manual verification.
 +
*PO Template for '''Expired transactions''' (authorized transactions, but completed AFTER the time frame allowed by to merchant for authorization completion has passed - authorization DELTA T) - '''<f_auth_minutes>''' TAG from '''f_message'''
 +
 +
'''NOTE''': By using this method, '''SESSION''' variables related to HTTP communication between merchant server and customer's Browser '''CANNOT''' be used on the merchant's server.
  
−
'''ATENTIE''' acesta metoda '''NU''' este recomandata website-urilor care nu utilizeaza SSL!
+
'''NOTE''': this method is recommended for websites that do not use SSL!
  
−
<br />Colectia QueryString contine setul de parametrii trimisi de comerciant in '''F_Message''' la sectiunea '''&lt;f_relay_response_url&gt;''' la cererea de Autorizare si parametrii Plati Online:
+
<br/> '''SOAP XML''' contain '''f_relay_message''' and '''f_crypt_message''' and merchant's soap tags. Use this schema to validate: '''[http://secure2.plationline.ro/xml_validation/auth.soap.response.v5.xsd http://secure2.plationline.ro/xml_validation/auth.soap.response.v5.xsd]'''
  
 +
&nbsp;
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! Parametru Authorizare !! Tipul de data !! Descriere
+
! Tag
 +
! Data type
 +
! Comments
 
|-
 
|-
−
| PO_RELAY_MESSAGE || text || Rezultatul incriptarii campului '''F_MESSAGE_RELAY'''.<br />[[Ce contine campul '''F_MESSAGE_RELAY'''?]]
+
| f_relay_message
 +
| string
 +
| Authorization XML relay response '''[https://secure.plationline.eu/xml_validation/auth.response.v5.xsd https://secure.plationline.eu/xml_validation/auth.response.v5.xsd]''' encrypted with '''AES algorithm'''
 
|-
 
|-
−
| Orice alt parametru || text || Parametrii trimisi la cererea de autorizare: [[Datele_necesare_pentru_AUTORIZARE_PO_Versiunea_4.x|Datele necesare pentru AUTORIZARE PO Versiunea 4.x]]
+
| f_crypt_message
 +
| text
 +
| '''AES Key''' (used for encrypting '''Authorization XML relay response''') encrypted with RSA ITSN pair keys
 +
|-
 +
| merchant_SoapTags
 +
| complex
 +
| SoapTags used on Authorization XML request on tags '''//merchants_fields//SoapTags''';XML schema '''[https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd]'''
 
|}
 
|}
  
 +
=== SOAP (Direct PlatiOnline Server - Merchant Server) - Merchants HTML Page ===
  
 +
:Using this method allows a direct communication between servers without involving customer's Browser.
 +
:PO Server will post directly to merchant's URL by:
  
−
=== SOAP (Direct PlatiOnline Server - Merchant Server) - PlatiOnline Template ===
+
*'''Content-Type="application/soap+xml; charset=utf-8"''';
 +
*'''SOAPAction=RelayResponse''';
  
−
: Utilizarea acestei metode permite o comunicare directa intre servere fara sa implice Browserul clientului.
+
:Merchant's server processes transaction result and response to PO Server with a XML code;  
−
# Serverul PO face POST direct la URL-ul  comerciantului prin "Content-Type" = "application/soap+xml; charset=utf-8";
 
−
# Serverul Comerciantului prelucreaza rezultatul tranzactiei si raspunde serverului PO cu un cod XML;<br />
 
  
 +
'''NOTE''': By using this method, '''SESSION''' variables related to HTTP communication between merchant server and customer's Browser '''CANNOT''' be used on the merchant's server.
  
−
: In functie de rezultat avem urmatoarele template-uri:
+
'''NOTE''': this method is recommended for websites that do not use SSL!
−
# Template PO tranzactiile '''Aprobate''';
 
−
# Template PO tranzactiile '''Respinse'''. In acest template afisam mesajul de decline si oferim posibilitatea clientului sa reincerce tranzactia prin apasarea unui buton;
 
−
# Template PO tranzactiile '''In curs de verificare'''. In acest template clientul este informat ca trebuie sa astepte intrucat tranzactia trebuie verificata manual;
 
−
# Template PO pentru tranzactiile '''Expirate''' ('''Aprobate''' dar finalizeate DUPA ce timpul alocat de comerciant pentru efectuarea operatiei de '''Autorizare''' pentru comanda respectiva a trecut (Delta T pentru autorizare).<br/>Tagul '''&lt;f_auth_minutes&gt;''' din campul F_Message [[Formatul_campului_F_Message_pentru_operatia_de_AUTORIZARE|Formatul campului F_Message pentru operatia de AUTORIZARE]]
 
−
 
 
−
 
 
−
'''ATENTIE''' utilizand acesta metoda, pe serverul comerciantului '''nu se pot utiliza variabilele SESSION''' din comunicarea '''HTTP''' dintre '''serverul comerciantului''' si '''Browserul clientului'''.
 
−
 
 
−
'''ATENTIE''' acesta metoda este recomandata website-urilor care nu utilizeaza SSL!
 
  
 +
<br/> '''SOAP XML''' contain '''f_relay_message''' and '''f_crypt_message''' and merchant's soap tags. Use this schema to validate: '''[http://secure.plationline.eu/xml_validation/auth.soap.response.v5.xsd http://secure.plationline.eu/xml_validation/auth.soap.response.v5.xsd]'''
  
−
<br />Colectia '''POST''' contine setul de parametrii trimisi de comerciant in '''F_Message''' la sectiunea '''&lt;f_relay_response_url&gt;''' la cererea de Autorizare si parametrii Plati Online:
+
&nbsp;
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
−
! Parametru Authorizare !! Tipul de data !! Descriere
+
! Tag
 +
! Data type
 +
! Comments
 +
|-
 +
| f_relay_message
 +
| string
 +
| Authorization XML relay response '''[https://secure.plationline.eu/xml_validation/auth.response.v5.xsd https://secure.plationline.eu/xml_validation/auth.response.v5.xsd]''' encrypted with '''AES algorithm'''
 +
|-
 +
| f_crypt_message
 +
| text
 +
| '''AES Key''' (used for encrypting '''Authorization XML relay response''') encrypted with RSA ITSN pair keys
 
|-
 
|-
−
| PO_RELAY_MESSAGE || text || Rezultatul incriptarii campului '''F_MESSAGE_RELAY'''.<br />[[Ce contine campul '''F_MESSAGE_RELAY'''?]]
+
| merchant_SoapTags
 +
| complex
 +
| SoapTags used on Authorization XML request on tags '''//merchants_fields//SoapTags''';XML schema '''[https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd]'''
 
|}
 
|}

Latest revision as of 10:54, 22 May 2020

Payment Authorization Relay Response

On each transaction you can setup the relay response method:

Response method Comments
PTOR POST using JavaScript
POST_S2S_PO_PAGE POST server PO to merchant server, customer get the PO template
POST_S2S_MT_PAGE DEPRECATED - POST server PO to merchant server, customer get the Merchant template
SOAP_PO_PAGE POST SOAP server PO to merchant server, customer get the PO template
SOAP_MT_PAGE DEPRECATED - POST SOAP server PO to merchant server, customer get the Merchant template
GET DISABLED - it is imposible to use it starting Plati Online 5.0

Also merchants can setup a parameter to instruct Plati Online system to send the transaction decline response to the merchant's server.

 

PlatiOnline Authorization relay response

PlatiOnline Authorization result is automatically sent when acquiring bank accepts or declines amount authorization.
PlatiOnline.ro system provides several methods that allow merchants to receive transaction response:

POST (JavaScript PlatiOnline Server - Client Internet Browser - Merchant Server)

This method creates a HTML form where « action » parameter has merchant's URL f_relay_response_url.

  • Upon automated onLoad event, a JavaScript code will « submit » the form.
  • By using this method SESSION variables related to HTTP communication between merchant server and customer's Browser can be used.

NOTE: this method is NOT recommended for websites that do not use SSL!


POST QueryString contain f_relay_message and f_crypt_message:

Parameter Data type Comments
f_relay_message text Authorization XML relay response https://secure.plationline.eu/xml_validation/auth.response.v5.xsd encrypted with AES algorithm
f_crypt_message text AES Key (used for encrypting Authorization XML relay response) encrypted with RSA ITSN pair keys
merchant fields text QueryString used on Authorization XML request on tags //merchants_fields//PostQueryString;XML schema https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd

POST (Direct PlatiOnline Server - Merchant Server) - Merchant HTML Page

Using this method allows a direct communication between servers without involving customer's Browser.
  • PO Server will POST directly to merchant's URL;
  • Merchant server processes transaction result and responds to PO server with a HTML/JavaScript code;
  • PO Server saves HTML/JavaScript code and then sends it directly to customer's Browser.
  • The customer will view in Browser the merchant generated HTML/JavaScript response.

NOTE: By using this method, SESSION variables related to HTTP communication between merchant server and customer's Browser CANNOT be used on the merchant's server.

NOTE: this method is recommended for websites that do not use SSL!


SOAP XML contain f_relay_message and f_crypt_message and merchant's soap tags. Use this schema to validate: http://secure.plationline.eu/xml_validation/auth.soap.response.v5.xsd

 

Tag Data type Comments
f_relay_message string Authorization XML relay response https://secure.plationline.eu/xml_validation/auth.response.v5.xsd encrypted with AES algorithm
f_crypt_message text AES Key (used for encrypting Authorization XML relay response) encrypted with RSA ITSN pair keys
merchant_SoapTags complex SoapTags used on Authorization XML request on tags //merchants_fields//SoapTags;XML schema https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd

POST (Direct PlatiOnline Server - Merchant Server) - PlatiOnline Template

It's similar to above method, but customer will view authorization result in a PlatiOnline HTML format.
Depending on the transaction result, we provide the following templates:
  • PO Template for Authorized transactions;
  • PO Template for Declined transactions. In this template we provide a decline message and also allow the customer to retry the transaction by pressing one button;
  • PO Template for Pending Verification transactions. In this template customer is informed s/he must wait for final transaction result since transaction will undergo a manual verification.
  • PO Template for Expired transactions (authorized transactions, but completed AFTER the time frame allowed by to merchant for authorization completion has passed - authorization DELTA T) - <f_auth_minutes> TAG from f_message

NOTE: By using this method, SESSION variables related to HTTP communication between merchant server and customer's Browser CANNOT be used on the merchant's server.

NOTE: this method is recommended for websites that do not use SSL!


POST QueryString contain f_relay_message and f_crypt_message:

Parameter Data type Comments
f_relay_message text Authorization XML relay response https://secure.plationline.eu/xml_validation/auth.response.v5.xsd encrypted with AES algorithm
f_crypt_message text AES Key (used for encrypting Authorization XML relay response) encrypted with RSA ITSN pair keys
merchant fields text QueryString used on Authorization XML request on tags //merchants_fields//PostQueryString;XML schema https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd

GET (Redirect PlatiOnline Server - Client Internet Browser - Merchant Server)

DISABLED

SOAP (Direct PlatiOnline Server - Merchant Server) - PlatiOnline Template

Using this method allows a direct communication between servers without involving customer's Browser.
PO Server will post directly to merchant's URL by:
  • Content-Type="application/soap+xml; charset=utf-8";
  • SOAPAction=RelayResponse;
Merchant's server processes transaction result and response to PO Server with a XML code;
  • PO Template for Authorized transactions;
  • PO Template for Declined transactions. In this template we provide a decline message and also allow the customer to retry the transaction by pressing one button;
  • PO Template for Pending Verification transactions. In this template customer is informed s/he must wait for final transaction result since transaction will undergo a manual verification.
  • PO Template for Expired transactions (authorized transactions, but completed AFTER the time frame allowed by to merchant for authorization completion has passed - authorization DELTA T) - <f_auth_minutes> TAG from f_message

NOTE: By using this method, SESSION variables related to HTTP communication between merchant server and customer's Browser CANNOT be used on the merchant's server.

NOTE: this method is recommended for websites that do not use SSL!


SOAP XML contain f_relay_message and f_crypt_message and merchant's soap tags. Use this schema to validate: http://secure2.plationline.ro/xml_validation/auth.soap.response.v5.xsd

 

Tag Data type Comments
f_relay_message string Authorization XML relay response https://secure.plationline.eu/xml_validation/auth.response.v5.xsd encrypted with AES algorithm
f_crypt_message text AES Key (used for encrypting Authorization XML relay response) encrypted with RSA ITSN pair keys
merchant_SoapTags complex SoapTags used on Authorization XML request on tags //merchants_fields//SoapTags;XML schema https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd

SOAP (Direct PlatiOnline Server - Merchant Server) - Merchants HTML Page

Using this method allows a direct communication between servers without involving customer's Browser.
PO Server will post directly to merchant's URL by:
  • Content-Type="application/soap+xml; charset=utf-8";
  • SOAPAction=RelayResponse;
Merchant's server processes transaction result and response to PO Server with a XML code;

NOTE: By using this method, SESSION variables related to HTTP communication between merchant server and customer's Browser CANNOT be used on the merchant's server.

NOTE: this method is recommended for websites that do not use SSL!


SOAP XML contain f_relay_message and f_crypt_message and merchant's soap tags. Use this schema to validate: http://secure.plationline.eu/xml_validation/auth.soap.response.v5.xsd

 

Tag Data type Comments
f_relay_message string Authorization XML relay response https://secure.plationline.eu/xml_validation/auth.response.v5.xsd encrypted with AES algorithm
f_crypt_message text AES Key (used for encrypting Authorization XML relay response) encrypted with RSA ITSN pair keys
merchant_SoapTags complex SoapTags used on Authorization XML request on tags //merchants_fields//SoapTags;XML schema https://secure.plationline.eu/xml_validation/f_message.auth.v5.xsd
Retrieved from "https://wiki.plationline.eu/index.php?title=Authorization_relay_response&oldid=281"