PlatiOnline API - software developers
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:
| Field name | Comments |
|---|---|
| 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:
| Step | Comments |
|---|---|
| 1. 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 authorization in the Plati Online system; |
| 2. 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. |
| 3. Authorization relay response Authorized/Declined/On Hold | Once the card is processed, the Plati Online system will send to merchant's server the response:
|
