Wallet API is composed of two different, but related features:
First of all, before continuing you should read the documentation to find out if it's the right tool, which you are looking for.
There are two types of accounts which could be used with an integration:
Productionis used as a real environment. To obtain an account register in Paysera.
Sandboxis used as a developing environment. To obtain an account, register in Paysera Sandbox.
Contact Paysera with a description of how are you going to use specific API, which API will be used
and will it be used with
Sandbox. You might be asked to provide
Signing an agreement can be skipped if Sandbox environment will be used, but we strongly advise to sign an agreement
at any case, as only with an agreement you might be sure,
that we will allow using our services in
Read the chapter about Authentication and choose the method you prefer, inform Paysera about your selection. It takes time to configure all, so when it will be ready, we will send credentials to your specified address.
Production environments are different, so you won't be able to use the same
credentials from one environment on another.
Sandboxclient can be configured without an agreement, while
Productionclient requires an agreement.
All API calls must be authenticated. Currently, two authentication schemes are used:
In any case, all requests to the Paysera system are made using HTTPS protocol. Paysera system always authenticates the client, but the client needs to be sure that the authentication on Paysera server is performed too. For all API calls, the certificate of Paysera server must be checked for validity. This protects from DNS spoofing, MITM, and similar attacks.
MAC access authentication used in API is based on the OAuth 2.0 Message Authentication Code (MAC) Tokens specification.
Before using API, you must register your app in Paysera system. Public registration is not yet available, please contact our support to register the client for this API. You will be provided with your credentials, for example:
client_id: wkVd93h2uS mac_key: IrdTc8uQodU7PRpLzzLTW6wqZAO6tAMU mac_algorithm: hmac-sha-256
mac_keymust be kept secret at all times.
At each request to API the client must construct an authentication header by calculating the UNIX
generating a random string used as a
nonce. From these values, together with the HTTP request method,
request URI, hostname, port and
mac_key, the client has to calculate hash using the algorithm
mac_algorithm. This calculated hash is
mac value, which must be included in the
MAC) and the following parameters:
id- ID assigned to the client making the request (
ts- calculated UNIX timestamp;
nonce- randomly generated value; only characters in ranges %x20-21 / %x23-5B / %x5D-7E can be used;
mac- calculated hash of request values and
ext- extension to MAC protocol. May contain parameter
body_hashand extra parameters
location_id. Parameters are URL-encoded.
body_hashis the result of sha256 and base64 encoded request content if it's present. If there is no content,
body_hashshould be omitted.
extcan be empty if there are no parameters, including
GET /rest/v1/payment/10145 HTTP/1.1 Host: wallet.paysera.com User-Agent: PayseraApi library Authorization: MAC id="wkVd93h2uS", ts="1343818800", nonce="nQnNaSNyubfPErjRO55yaaEYo9YZfKHN", mac="xTCR/i6LKbhXoo4Fe77ECowrn+Q6uUdX7yxwS/lhDWU=", ext="body_hash=ob%2FZf8GBHrgpuw5xc3esSw2NYiOG9N9AQKAm%2FMpElfs%3D&project_id=1"
macvalue is calculated from the normalized request string and
\nin most of programming languages):
Hostrequest header in lower case;
extfield - URL-encoded string containing various extra parameters.
GET /rest/v1/payment/10145 HTTP/1.1 Host: wallet.paysera.com User-Agent: PayseraApi library
1343818800\n nQnNaSNyubfPErjRO55yaaEYo9YZfKHN\n GET\n /rest/v1/payment/10145\n wallet.paysera.com\n 443\n \n
macis calculated using HMAC algorithm together with the sha256 hash function:
mac = HMAC-SHA256(mac_key, normalizedRequestString)
Please refer to HMAC and SHA256 specifications for more details on these algorithms.
The result is provided as a binary result, encoded in base64.
When using this authentication scheme, no additional headers are needed. To register the certificate with Paysera system, the certificate request must be provided for our administrators to generate the signed certificate.
Before generating the certificate request, a private key must be generated. Always keep the private key securely and don't disclose it even to Paysera administrators.
For example, the certificate request can be generated using openssl command line client:
openssl genrsa -out private.pem 2048 openssl req -new -key private.pem -out certificate_request.csr Country Name (2 letter code) [AU]:LT State or Province Name (full name) [Some-State]: Locality Name (eg, city) :Vilnius Organization Name (eg, company) [Internet Widgits Pty Ltd]:UAB Some Company Organizational Unit Name (eg, section) : Common Name (e.g. server FQDN or YOUR name) :example.com Email Address :firstname.lastname@example.org
An optional company name when generating a certificate request