The payment flows that you can use with Meal Vouchers are:

MATCH_CODE DOC
This flow can be used generically for one-off payments.

HOTP_AUTH DOC
This flow can be used to perform one-off payments via HOTP tokens.
To use this flow you must also include the token parameter.

MATCH_USER DOC
This flow can be used for one-off payments on a specific user.
To use this flow you must also include the consumer_uid parameter.

REFUND DOC
This flow can be used for refunds on a specific payment.
To use this flow you must also include the parent_payment_uid and the amount_unit.

The payment currency.

Currently EUR is the only currency supported.

The token required to charge the consumer wallet.
It can be an HOTP token.

Required with HOTP_AUTH flow only.

The unique id of the consumer required for payment acceptance.
To obtain the customer id, please use the Get Consumer API.

Required with MATCH_USER flow only.

This parameter is deprecated; we suggest avoiding the MATCH_USER UX unless absolutely necessary.

The id of the payment that you want to refund.

Required with REFUND flow only.

The external order id or payment identifier.

We highly recommend to use this field by populating it with your internal order id.
This string will be included in your reports for reconciliation and shown to the Satispay consumer in-app.

This field has a maximum length of 50 characters, including spaces.

The URL to be triggered via an HTTP GET request when there is a change in payment status.

When the given callback_url is invoked, a GET request for payment details can be made to retrieve the updated payment status.

Please note that {uuid} will be replaced with the generated payment id.
e.g. https://example.com/satispay-callback?payment_id={uuid}

You can read more here.

This field specifies the URL where the user will be redirected after the payment flow from the Satispay app is completed.

For instance, you can set this URL to ensure users are redirected to that specific page upon successful payment completion.
e.g. https://example.com/payment-redirect?order_id=your_order_id

Please note that this field doesn't support any placeholder.

The UTC payment expiration datetime.

The format should be ISO 8601 like this yyyy-MM-dd'T'HH:mm:ss.SSSZ.

By default MATCH_CODE and MATCH_USER payments are valid for 2 hours.

This parameter cannot be used with HOTP_AUTH and REFUND flows.

Always send this header as application/json.

The host declared in the signature.

The date declared in the signature.

The digest declared in the signature.

The request signature.

The idempotent request key.

You can read more here.

The device information (e.g., hostname).

The device type.

The Operating System name (e.g., Windows).

The Operating System version (e.g., 10).

The software house name (e.g., Satispay).

The software name (e.g., My awesome app).

The software version (e.g., v2.0.0).

The tracking code used by Satispay commercial partners.

Use this code only if explicitly required by Satispay.