Инструменты страницы
Содержание
Request to create a customer profile
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).
List of the request parameters:
Parameter | Type | Mandatory | Description | Value example |
---|---|---|---|---|
|
string | Yes |
A unique transaction number on the partner's side is required to maintain idempotence of transactions. | 7654321DS |
| string | Yes |
The partner identifier you received when registering in the payment gateway. | petrovich |
|
array | Yes |
Array of customer data | |
|
Name
Typestring DescriptionGeneral
Type of contact mean to be transferred. The following values are available:
sbersafeSpecifying the entity type, the following values are possible:
| Yes |
Type of contact mean to be transferred. The following values are available:
| EMAIL |
| string | Yes |
Value of the contact mean. | test@test.ru |
Request format:
POST /api/clients/create HTTP/1.1 Host: 3dsec.sberbank.ru/sbersafe Content-Type: application/json Accept: application/json; version=1.0 Content-Length: <content-lenght> { "transactionNumber":"<transactionNumber>", "merchantLogin":"<merchantLogin>", "contacts": [ { "type": "<type>", "value": "<value>" }, { "type": "<type>", "value": "<value>" } ] }
Response parameters:
Parameter | Type | Mandatory | Description | Value example |
---|---|---|---|---|
|
object | Yes |
Array of customer information |
|
| string | Yes |
Customer identifier, length 32. | C2BC84C12AD6438DAA0D87517C7AE187 |
|
date | Yes |
Date of the customer creation. | 07.09.2017 17:43:57.768 |
|
string | Yes |
Access code generated by the payment gateway. | i1WsRn1uB1ehfbb37 |
|
string | Yes |
Request identifier. | gbhjnkme-rdcfgv-hbjnkm-7689ui-okp3ew |
|
string | Yes |
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 { "client": { "uuid": "<clientUuid>", "createdDate": "<createdDate>" }, "accessCode":"<accessCode>", "requestId": "<requestId>", "status": "<status>" }