Submit a previously setup payment
This API is secured with oAuth 2.0 and you can complete the API call by :
Step 1: You need an "authorization_code" access token. Either set the Authorization header with access token obtained here or click on the "OAuth 2.0 Set" button in "Try it out" section below to complete the oAuth flow, get the access token( which is then set it automatically and "Set" on oAuth 2.0 button changes to "authenticated").
Step 2: All POST calls need a x-jws-signature header. Set the header by clicking "Create JWT button beside the x-jws-signature header field". This gets the payload from request body editor and creates the x-jws-signature for it.
Step 3: Try the API
(required)Every request will be processed only once per x-idempotency-key. The Idempotency Key will be valid for 24 hours.
(required)The unique id of the ASPSP to which the request is issued. The unique id will be issued by OB.
x-fapi-customer-last-logged-timeThe time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
x-fapi-customer-ip-addressThe PSU's IP address if the PSU is currently logged in with the TPP.
x-fapi-interaction-idAn RFC4122 UID used as a correlation id.
AuthorizationAn Authorisation Token as per https://tools.ietf.org/html/rfc6750
(required)Header containing a detached JWS signature of the body of the payload.
(required)Content type of the payload.
This is the place where EventTypes description lies.
Sample Error Messages & Error Codes.
This is where error messages sample and description lies.
This is the place where HTTP Status Codes.