Payment Information Bulk Request

The call
/v1/banking/pis/payments/{payment-product}
has one field service-session-id in header which is the clients handle to the consent the payment information is requested for. It would make sense to have a bulk request with a bulk of consent handles as input.

Further the order of the returned elements must stick to the order of the handles passed in. Otherwise additional information stored in fintech (like initiation date) can not be merged to result.