Create payment - v2
Create payment with specific type: POS, Ecommerce, ScanAndPay, ManualTopUp, SubscriptionTopUp. If requestMemberConfirmation = true, then this payment should be confirmed by member. Otherwise - will try to confirm payment automatically using ‘Bonus’ payment type.
Authorizations
JWT Authorization header using the Bearer scheme. Example: "Authorization: Bearer {token}"
Body
Payment type.
1Id of member who checked in on the POS, who suppose to pay for the purchase Must contain latin alphanumeric characters, max length 32. Allowed special characters: '-', '_'
1 - 36Unique identifier of initiate payment operation (should be same only for retries of the same operation)
1 - 64Amount to pay
x >= 0Payment location. Required only for POS payments.
128Store ID. Required only for Ecommerce, ScanAndPay payments.
64Unique payment identifier. Required for POS, Ecommerce, ScanAndPay payments.
64Determines whether member confirmation is needed for this payment
List of payment methods chosen for payment. This parameter is optional. Currently only required for ManualTopUp, SubscriptionTopUp payments.
1Indicates whether a capture of the reservation is instantaneous. This parameter is optional. Currently only required for ManualTopUp, SubscriptionTopUp payments.
Indicates whether the payment is recurring. This parameter is optional. Currently only used for SubscriptionTopUp payments.
Response
OK
Payment id used to manage initiated payment and retrieve payment status
1