Difference between revisions of "Validating the XML Message validation schema"

From PlatiOnline.EU
Jump to: navigation, search
m
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
 
== XML Authorization ==
 
== XML Authorization ==
  
 
'''Plati Online version 5.x'''
 
'''Plati Online version 5.x'''
−
#Post URL: https://secure.plationline.eu/
+
 
−
#Request XML validation schema: https://secure2.plationline.ro/xml_validation/po.request.v5.xsd
+
#Post URL: '''[https://secure.plationline.ro/ https://secure.plationline.ro/]'''
−
#XML_Message validation schema: https://secure2.plationline.ro/xml_validation/f_message.auth.v5.xsd
+
#Request XML validation schema: '''[https://secure.plationline.ro/xml_validation/po.request.v5.xsd https://secure.plationline.ro/xml_validation/po.request.v5.xsd]'''
 +
#XML_Message validation schema: '''[https://secure.plationline.ro/xml_validation/f_message.auth.v5.xsd https://secure.plationline.ro/xml_validation/f_message.auth.v5.xsd]'''
  
 
Pseudo-code:
 
Pseudo-code:
−
#Create the XML_Message;
+
 
−
#SOAP heders:
+
#Create the XML_Message  
−
#*CONTENT_TYPE = '''text/xml; charset=utf-8'''
+
##for '''Payment Tokenization''' you can get the '''x_payment_token '''using '''API Query Request'''  
−
#*USER_AGENT = '''PlatiOnline-SOAP'''
+
##for SCA you can get '''oauth_payment_token''' implementing '''Login with Plati.online''' method 
−
#*HTTP_SOAPACTION = '''auth-only'''
+
#Create a random 32 alphanumeric '''AES KEY''';  
−
#Create a random 32 alphanumeric AES KEY;
+
#Encrypt the '''AES KEY''' with the '''RSA''' algorithm, this is the value of '''f_crypt_message''' tag;  
−
#Encrypt the AES KEY with the RSA algorithm, UrlEncode this hash (this is the value of F_CRYPT_MESSAGE);
+
#Encrypt the '''XML_Message''' with the AES algorithm using the '''AES KEY''' and the '''IV_AUTH''', this is the value of '''f_message''' tag;  
−
#Encrypt the XML_Message with the AES algoritm using the AES KEY and the IV_AUTH, UrlEncode this hash (this is the value of F_MESSAGE field);
+
#Validate the '''Request XML''' using '''[https://secure.plationline.ro/xml_validation/po.request.v5.xsd https://secure.plationline.ro/xml_validation/po.request.v5.xsd]'''
−
#Post the F_LOGIN, F_MESSAGE and F_CRYPT_MESSAGE to https://secure.plationline.eu/
+
#Post SOAP (version 1.1 or 1.2) to [https://secure.plationline.ro/ https://secure.plationline.ro/]
 +
#*If you use SOAP 1.1 headers are:
 +
#*#CONTENT_TYPE = '''text/xml; charset=utf-8'''
 +
#*#USER_AGENT = '''PlatiOnline-SOAP'''
 +
#*#SOAPACTION = '''auth-only''' 
 +
#*If you use SOAP 1.2 headers are:
 +
#*#CONTENT_TYPE = '''application/soap+xml; charset=utf-8; action=auth-only'''
 +
#*#USER_AGENT = '''PlatiOnline-SOAP'''

Latest revision as of 19:11, 30 April 2020

XML Authorization

Plati Online version 5.x

  1. Post URL: https://secure.plationline.ro/
  2. Request XML validation schema: https://secure.plationline.ro/xml_validation/po.request.v5.xsd
  3. XML_Message validation schema: https://secure.plationline.ro/xml_validation/f_message.auth.v5.xsd

Pseudo-code:

  1. Create the XML_Message
    1. for Payment Tokenization you can get the x_payment_token using API Query Request
    2. for SCA you can get oauth_payment_token implementing Login with Plati.online method
  2. Create a random 32 alphanumeric AES KEY;
  3. Encrypt the AES KEY with the RSA algorithm, this is the value of f_crypt_message tag;
  4. Encrypt the XML_Message with the AES algorithm using the AES KEY and the IV_AUTH, this is the value of f_message tag;
  5. Validate the Request XML using https://secure.plationline.ro/xml_validation/po.request.v5.xsd
  6. Post SOAP (version 1.1 or 1.2) to https://secure.plationline.ro/
    • If you use SOAP 1.1 headers are:
      1. CONTENT_TYPE = text/xml; charset=utf-8
      2. USER_AGENT = PlatiOnline-SOAP
      3. SOAPACTION = auth-only
    • If you use SOAP 1.2 headers are:
      1. CONTENT_TYPE = application/soap+xml; charset=utf-8; action=auth-only
      2. USER_AGENT = PlatiOnline-SOAP
Retrieved from "https://wiki.plationline.eu/index.php?title=Validating_the_XML_Message_validation_schema&oldid=277"