Verify

Verify  request is used for performance of client’s card verification.

The result of request processing is the blocking of monetary assets on the client’s card and automatic unblocking of the assets upon expiration of 60 minutes

 

Request parameters

The request with required parameters is to be formed on the side of merchant and to be transferred by POST method through HTTP protocol to URL https://api.wayforpay.com/api

For the purposes of confirmation of data validity there should be generated and transferred in the request the HMAC_MD5 control signature using SecretKey of merchant.

The line which subjects to HMAC_MD5 is generated through catenation of parameters  merchantAccount, merchantDomainName, orderReference, amount, currency  divided with “;” (semi-column) in coding UTF-8

 

PARAMETER

DESCRIPTION

MANDATORY

transactionType

VERIFY

 

merchantAccount

Seller identifier

yes

merchantAuthType

Authorization type. May take one of the following values:

  • simpleSignature (default)

no

merchantDomainName

Domain name of merchant’s web-site

yes

merchantSignature

Request signature

yes

apiVersion

The protocol version. Default value: 1

yes

serviceUrl

URL, to which the system should send to Merchant a response with the result of the payment

no

orderReference

Unique number of the order in merchant’s system

yes

amount

Amount verify

0 - for generate free amount on  wayforpay side , within 1-5grn.

yes

currency

currency verify: UAH

yes

card

Card number 16 characters

yes

expMonth

Card Expiry Date (mounth)

 - MM

yes

expYear

Card Expiry Date (year)- YY

yes

cardCvv

Card Security Code CVV / CVV2

yes

cardHolder

Cardholder Name, as indicated on the card

yes

clientEmail

Client Email

no

clientPhone

Client Phone

no

clientCountry

Client Country

no

clientAddress

Client address

no

clientCity

Client city

no

clientState

Client state/region

no

clientZipCode

Client postal code

no

Response parameters

For the purposes of confirmation of data validity there should be generated and transferred in the request the HMAC_MD5 control signature using SecretKey of merchant.

The line which subjects to HMAC_MD5 is generated through catenation of parameters  merchantAccount, orderReference, amount, currency, authCode, cardPan, transactionStatus, reasonCode  divided with “;” (semi-column) in coding UTF-8

 

PARAMETER

DESCRIPTION

EXAMPLE

merchantAccount

Seller identifier

test_merchant

orderReference

Unique number of the order in merchant’s system

1212dd1

merchantSignature

hash_hmac

 

amount

amount verify

100

currency

currency verify

UAH

authCode

authorization code - assigned by Bank

324567

createdDate

 Date of creation request  in psp (UTC)

123456789

processingDate

date of transaction processing (UTC)

12345678

cardPan

Masked card number (44****4444)

42****4242

cardType

Card Type: Visa/MasterCard

Visa

issuerBankCountry

Country of card

980

issuerBankName

Name of the Bank card

PrivatBank

recToken

card token for recurring payments

121213321-3213213-3213213-321-3

transactionStatus

transaction status

Approved

reason

Reason for refusal

Ok

reasonCode

Code of refusal

1100

fee

Commission psp

0.00

paymentSystem

The payment system, through which the payment was made.

card

 

An example of request and response

Request:
{
"transactionType":"VERIFY",
"merchantAccount":"test_merch",
"merchantAuthType":"SimpleSignature",
"merchantDomainName":"www.bistrozaim.ua",
"merchantSignature":"60c5d743b71f79abe48c7183ada4b451",
"apiVersion":1,
"orderReference":"myOrder1",
"amount":1.13,
"currency":"UAH",
"card":"4111111111111111",
"expMonth":"11",
"expYear":"2020",
"cardCvv":"111",
"cardHolder":"TARAS BULBA",
"clientFirstName":"Bulba",
"clientLastName":"Taras",
"clientCountry":"UA",
"clientEmail":"rob@mail.com",
"clientPhone":"380556667788"
}

 

response (request on serviceUrl)
{
"merchantAccount":"test_merchant",
"orderReference":"DH783023",
"merchantSignature":"",
"amount":1.13,
"currency":"UAH",
"authCode":"541963",
"createdDate":12345678,
"processingDate":12345678,
"cardPan":"41****8217",
"cardType":"visa",
"issuerBankCountry":"980",
"issuerBankName":"Privatbank",
"recToken":"121213321-3213213-3213213-321-3",
"transactionStatus":"Approved",
"reason":"",
"reasonCode":1100,
"fee":0,
"paymentSystem":"card"
}

 

Example of correct response from the merchant

WayForPay system expects to obtain the following response from the merchant’s server:

{
"orderReference":"DH783023",
"status":"accept",
"time":1415379863,
"signature":""
}

The line which subjects to HMAC_MD5 is generated through catenation of parameters  orderReference, status, merchantSecretKey  divided with “;” (semi-column) in coding UTF-8For the purposes of confirmation of data validity there should be generated and transferred in the request the HMAC_MD5 control signature using SecretKey of merchant.

Notification of merchant about the status of transaction

For authorized and checked orders (as well as in case of change of order status) WayForPay server sends to serviceUrl  a request (HTTP_POST) which includes the order data.

This information is to be supplemented with a control signature HMAC_MD5.