1.2.11. MFO Scoring by NSPK

Making direct requests

MFO scoring allows to score card for purposes of MFO (Micro-Financial Organization).

MFO scoring flow

Merchant initiates request for MFO scoring by sending HTTPS POST request to the specified URL of the Merchant`s endpoint on gate.payneteasy.com. After that, Payneteasy system returns response with MFO scoring response data set.

MFO scoring URL

https://gate.payneteasy.com/paynet/api/scoring/v1/score/ENDPOINT

for integration purposes use staging environment sandbox.payneteasy.com instead of production gate.payneteasy.com

Each request is supposed to have its own unique client order ID. A request must be made using the HTTP POST method with UTF-8 encoding. Each parameter is to be supplied as a POST request parameter (using application/x-www-form-urlencoded).

Each request must be signed (see below). The signature must be put to X-Authorization request header.

A response is in JSON format (in UTF-8 encoding).

Request parameters

MFO scoring HTTP POST request body may have two different sets of parameters which are accepted by the system, as you may see below:

1. card-ref-id or card-number
2. client-order-id

Note

Request must have content-type=application/x-www-form-urlencoded and Authorization headers.

Request parameter name	Format	Description
card-ref-id	N{1-*}	the card-ref-id created earlier using create-card-ref call that can be used to find the specific card that is needed
card-number	N{13-19}	Full card number
client-order-id	N{1-*}	Client number in the system
first-name	N{64}	First Name
last-name	N{64}	Last Name
middle-name	N{64}	Middle Name
birth-date	1982-07-31	Client number in the system
rating	N{4}	For example 0000
phone	N{11}	Customer’s full international phone number, including country code

Request debug

HTTP method
URL
parameters
version
consumer key
consumer secret
timestamp
nonce
signature method

normalized parameters

signature base string

signature

authorization header

Curl
Copy to clipboard

Response data

Note

Response has Content-Type: text/html;charset=utf-8 header. All parameters in response are x-www-form-urlencoded, with (0xA) character at the end of each parameter’s value

Parameter name	Description
type	The type of response. May be async-response, validation-error, error. If type equals validation-error or error, error-message and error-code parameters contain error details.
paynet-order-id	Order id assigned to the order by Payneteasy
merchant-order-id	Merchant order id
serial-number	Unique number assigned by Payneteasy server to particular request from the Merchant.
error-message	If status is error this parameter contains the reason for decline or error details
error-code	The error code is case of error status

Scoring status

Merchant must use Scoring status API call to get the customer’s order transaction status. After any type of transaction is sent to Payneteasy server and order id is returned, Merchant should poll for transaction status. When transaction is processed on Payneteasy server side it returns it’s status back to Merchant and at this moment the Merchant is ready to show the customer transaction result, whether it’s approved or declined.

Scoring status request parameters

Status call parameters	Description
login	Merchant login name
client_orderid	Merchant order identifier of the transaction for which the status is requested
orderid	Order id assigned to the order by Payneteasy

Scoring status request debug

HTTP method
URL
parameters
version
consumer key
consumer secret
timestamp
nonce
signature method

normalized parameters

signature base string

signature

authorization header

Curl
Copy to clipboard

Scoring status response data

Parameter name	Description
type	The type of response. May be status-response
serial-number	Unique number assigned by Payneteasy server to particular request from the Merchant.
status	The status code of the initial transaction. May be approved, declined, processing, error or filtered. It type equals filtered it means the transaction was considered fraudulent by Payneteasy Server.
client-order-id	Client order id
paynet-order-id	Order id assigned to the order by Payneteasy
card-ref-id	ID generated by card-ref
bin	First 6 digits of the card
last-four-digits	Last 4 digits of the card
bank-name	Card Bank Name
scoring-service-request-id	Scoring service request ID
scoring-service-response-id	Scoring service response ID
score1	Scoring score 1
score2	Scoring score 2
score3	Scoring score 3
scoring-service-response	Scoring service text response
error-message	If status in declined, error, filtered this parameter contains the reason for decline
error-code	The error code is case status in declined, error, filtered.