Инструменты страницы



Request for an auto-payment

In this document, the following data type conventions are used when describing request and response parameters:

  • string – string;
  • array – data array;
  • object – data object;
  • data – date;
  • boolean – boolean (logical) data type;
  • int. (integer) – integer data type;
  • amount – a numeric data type (amount).

Request parameters:

Parameter Type Description Example

transactionNumber

string

A unique transaction number on the partner's side is required to maintain idempotence of transactions.

7654321DS

source

object

The object of the payment source, only «card» or «binding» can be specified for passing.

card

object Data object with information about the source card.

pan

string

Payment card number.

5647637465647384

expiryDate

date

The validity of the card.

2018-07

cardholderName

string

Cardholder's name in Latin characters, if available.

IVAN PETROV

cvc

string

CVC/CVV2 code on the back of the card.

543

binding

string

Identifier.

87414E0F13AB4542AA9D10E81F74A6E3

preAuth

string

Parameter that defines the necessity of a pre-authorization (putting the amount on hold on the customer's account until its debiting). The following values are available:

  • true – the parameter is enabled, a payment is processed with a pre-authorization (the amount on the customer's account is put on hold until the debiting);
  • false – the parameter is disabled (the amount is debited immediately).

If the parameter is not specified in the request, the debiting occurs immediately; if it is specified, you must send a separate request for completion.

true

amount

object

Data object about the amount of payment.

transactionAmount

amount

Payment amount in minor currency units (61.00 rubles = 6100).

6100

transactionFee

amount

The amount of the commission for payment in minor currency units (1.00 rubles = 100).

200

currency

string Payment currency. 643

loyaltyPointsAmount

amount

Amount of «Spasibo» bonuses (in units of bonuses).

59

Request format:

POST /api/payment/autopayment HTTP/1.1
Host: web.rbsdev.com/sbersafe
Authorization: <accessToken>
Content-Type: application/json
Accept: application/json; version=1.0
Content-Length: <content-lenght>
{
  "transactionNumber":"<transactionNumber>",
  "source":{
     "card":{
        "pan":"<pan>",
        "expiryDate":"<expiryDate>",
        "cardholderName":"<cardholderName>",
        "cvc":"<cvc>"
        },
     "binding":"<binding>"
   },
  "preAuth":<true|false>,
  "amount":{
     "transactionAmount":<transactionAmount>,
     "transactionFee":<transactionFee>,
     "currency":"<currency>",
     "loyaltyPointsAmount":"<loyaltyPointsAmount>"
   }
}

Response parameters:

Parameter Type Description Example

mdOrder

string

Order number in the payment gateway. Unique within the payment gateway.

906bf262-bd53-4ac7-983c-07127954681b

transactionNumber

string

A unique transaction number on the partner's side is required to maintain idempotence of transactions.

7654321DS

requestId

string

Request identifier.

gbhjnkme-rdcfgv-hbjnkm-7689ui-okp3ew

status

string

Indication of the status of the request processing result

SUCCESS

Response format:

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: <content-lenght>
Cache-Control: no-store
   
{
  "mdOrder":"<mdOrder>",
  "transactionNumber":"<transactionNumber>",
  "requestId":"<requestId>",
  "status": "<status>"
}