Inquiries, InquiryItems
In case additional information about payer is needed (i.e. personal code) for client, it is possible to request it from payer on reserving Transaction.
To perform such action, you should create a Inquiry object, which acts as a container for a list of InquiryItem objects.
Then add newly created Inquiry (or some of them) as array to Transaction.
See Create transaction for more information.
Object structures
Inquiry
identifier
type
required, optional strings.
Flags whether or not current Inquiry is required.
items
description
status
accepted, declined strings.
Tells whether or not current Inquiry is accepted by the payer.
InquiryItem
identifier
type
types (see below).
title
types:
@deprecated person_code
- Payer will be informed, that his personal code will be given to client. This type will be removed in the future releases.
user_identity - Identity data structure (see identity data structure).
InquiryResult
inquiry_identifier
item_identifier
value
type.
Granting requested data
Workflow
Payer will be introduced to all data that client will receive after Transaction will be reserved. To avoid fraud, the display of Inquiry and InquiryItem data will be handled by Paysera.
After Transaction has been reserved, client can receive data by making request to inquired information resource. Only Inquiry objects, accepted by payer will be shown.
Inquired information resource
GET https://wallet.paysera.com/rest/v1/transaction/:transaction_key/inquired-informationAs a response, client will receive a list of InquiryResult objects as
items:
{
"items": [
{
"inquiry_identifier": "pDAlAZ3z",
"item_identifier": "k9rFrYb0",
"value": "12345678901"
}
]
}