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 /payment-submissions

  • Name
  • x-idempotency-key
    Every request will be processed only once per x-idempotency-key. The Idempotency Key will be valid for 24 hours.
  • x-fapi-financial-id
    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-time
    The 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-address
    The PSU's IP address if the PSU is currently logged in with the TPP.
  • x-fapi-interaction-id
    An RFC4122 UID used as a correlation id.
  • Authorization
    An Authorisation Token as per
  • x-jws-signature
    Header containing a detached JWS signature of the body of the payload.
  • Content-Type
    Content type of the payload.

Body Parameters

Name Values Description

Request Body

Setup a single immediate payment

Basic Auth

OAuth 2.0

Custom Token


Make a request and see the response.

Make a request and see the response.

Resource Summary


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.