createPaymentUsingPOST

URI of the TPP, where the user shall be redirected after consent authorization

If this URI is contained, the TPP is asking to redirect the transaction flow to this address instead of the TPP-Redirect-URI in case of a negative result of the redirect SCA method. This might be ignored by the ASPSP.

Client ID of the PSU in the ASPSP client interface.

Type of the PSU-ID; needed in scenarios where PSUs have several PSU-IDs as access possibility.

Specifies whether a redirect workflow is preferred for user consent signing. Specifies the TPP's preference for the authorization protocol to be used, however the final decision is made by the ASPSP.

ID of the request, unique to the call, as determined by the initiating party.

The forwarded IP Address header field consists of the corresponding HTTP request IP Address field between PSU and TPP.

TPP prefers to start the authorisation process separately or no

The forwarded accept language header field consist of the corresponding HTTP request accept header between PSU and TPP, if available. Expected format is LanguageTag-CountryTag where:
- LanguageTag is any two-letters matching an ISO-639 language abbreviation
- CountryTag is any two-letters matching an ISO-3166 country code and is optional

Combined service AIS Access token.

This data element may be contained, if the payment initiation transaction is part of a session, i.e. combined AIS/PIS service. This then contains the consentId of the related AIS consent, which was performed prior to this payment initiation.