Difference between revisions of "PlatiOnline API - software developers"
PlatiOnline (talk | contribs) (Created page with "== Plati Online API === Acest document ghideaza comerciantii noi in procesul de implementare a modulelor sistemului PO. Documentul ofera instructiuni de implementare pas cu pa...") |
PlatiOnline (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | == Plati Online API | + | == Plati Online API == |
Acest document ghideaza comerciantii noi in procesul de implementare a modulelor sistemului PO. Documentul ofera instructiuni de implementare pas cu pas asociate cu exemple de cod. Anexele documentului contin informatii utile cum ar fi tabele cu definitii ale termenilor utilizati des in industria cardurilor, codurile de eroare, codurile de judet si tara, alte informatii. | Acest document ghideaza comerciantii noi in procesul de implementare a modulelor sistemului PO. Documentul ofera instructiuni de implementare pas cu pas asociate cu exemple de cod. Anexele documentului contin informatii utile cum ar fi tabele cu definitii ale termenilor utilizati des in industria cardurilor, codurile de eroare, codurile de judet si tara, alte informatii. | ||
| − | === | + | === How to do requests to Plati Online === |
All the calls to/from Plati Online system use HTTP methods: | All the calls to/from Plati Online system use HTTP methods: | ||
| Line 11: | Line 11: | ||
| − | Every HTTP request between Plati Online system and the merchants servers are done using | + | Every HTTP request between Plati Online system and the merchants servers are done using 2 fields: |
| − | *'''F_MESSAGE''' | + | *'''F_MESSAGE''' - this field contain an XML encrypted with AES algorithm. For every call you/we have to generate a new AES key '''an random 32 length alphanumeric'''. |
| − | this field contain an XML encrypted with AES algorithm. For every call you/we have to generate a new AES key '''an random 32 length alphanumeric'''. | ||
| − | *'''F_CRYPT_MESSAGE''' | + | *'''F_CRYPT_MESSAGE''' - this field contain the AES key encrypted using the RSA algorithm. |
| − | this field contain the AES key encrypted using the RSA algorithm. | ||
| − | === Merchants security keys | + | === Merchants security keys === |
Cheile de securitete se utlizeaza pentru a identifica in mod unic tipul tranzactiei, suma, moneda si comerciantul in numele caruia se face tranzactia. | Cheile de securitete se utlizeaza pentru a identifica in mod unic tipul tranzactiei, suma, moneda si comerciantul in numele caruia se face tranzactia. | ||
| − | ==== [[Cum se obtin Cheile de securitate]] | + | ==== [[Cum se obtin Cheile de securitate]] ==== |
== Payment Authorization == | == Payment Authorization == | ||
| − | + | The authorization process is split-ed into 3 steps: | |
| − | Merchants will | + | |
| + | #Validating the XML_Message validation schema | ||
| + | Merchants will create the authorization XML named '''XML_Message''' request based on Plati Online version. | ||
| + | '''XML_Message''' contain all the necessary information to initiate an autorization in the Plati Online system; | ||
| + | |||
| + | #Redirect URL | ||
| + | Once the '''XML_Message''' is successfully parsed the Plati Online system will echo an XML with the redirect URL. | ||
| + | To continue transaction merchants have to send to the browser the '''URL HTTP Redirect'''; | ||
| + | Plati Online system will load the card page. | ||
| + | |||
| + | #Authorization Relay response [Authorized/Declined/On Hold] | ||
| + | Once the card is processed, the Plati Online system will send to merchant's server the response: | ||
| + | *Authorized | ||
| + | *Declined | ||
| + | *On Hold | ||
| + | |||
=== Plati Online version 5.0 === | === Plati Online version 5.0 === | ||
==== Authorization XML_Message XML validation schema ==== | ==== Authorization XML_Message XML validation schema ==== | ||
Revision as of 23:35, 14 March 2014
Contents
Plati Online API
Acest document ghideaza comerciantii noi in procesul de implementare a modulelor sistemului PO. Documentul ofera instructiuni de implementare pas cu pas asociate cu exemple de cod. Anexele documentului contin informatii utile cum ar fi tabele cu definitii ale termenilor utilizati des in industria cardurilor, codurile de eroare, codurile de judet si tara, alte informatii.
How to do requests to Plati Online
All the calls to/from Plati Online system use HTTP methods:
- POST
- GET
- SOAP
Every HTTP request between Plati Online system and the merchants servers are done using 2 fields:
- F_MESSAGE - this field contain an XML encrypted with AES algorithm. For every call you/we have to generate a new AES key an random 32 length alphanumeric.
- F_CRYPT_MESSAGE - this field contain the AES key encrypted using the RSA algorithm.
Merchants security keys
Cheile de securitete se utlizeaza pentru a identifica in mod unic tipul tranzactiei, suma, moneda si comerciantul in numele caruia se face tranzactia.
Cum se obtin Cheile de securitate
Payment Authorization
The authorization process is split-ed into 3 steps:
- Validating the XML_Message validation schema
Merchants will create the authorization XML named XML_Message request based on Plati Online version. XML_Message contain all the necessary information to initiate an autorization in the Plati Online system;
- Redirect URL
Once the XML_Message is successfully parsed the Plati Online system will echo an XML with the redirect URL. To continue transaction merchants have to send to the browser the URL HTTP Redirect; Plati Online system will load the card page.
- Authorization Relay response [Authorized/Declined/On Hold]
Once the card is processed, the Plati Online system will send to merchant's server the response:
- Authorized
- Declined
- On Hold
