QWqwist
Strong Customer Authentication

Solve synchronization challenge

Changed on

This endpoint is used to answer an authorization challenge that was issued by the financial provider. In addition to the normal transport layer encryption it is possible to encrypt the challenge response using JSON web encryption. Note that a challenge can only be answered once. Subsequent submission of a response to the same challenge will result in an error (HTTP status 409).

post/rest/accesses/{access-id}/syncs/{sync-id}/challenges/{challenge-id}/response

Request

Parameters

#/paths/~1rest~1accesses~1{access-id}/get/parameters/0 (unresolved $ref)
#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}/get/parameters/1 (unresolved $ref)
#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/parameters/2 (unresolved $ref)

Request body

OR
OR
OR

Example request

{
  "method_id": "M12345.6"
}

Response

Accepted.

Changes

  • 398592d93b1fRevision changes
    • breaking

      added the new path request parameter access-id

    • breaking

      added the new path request parameter challenge-id

    • breaking

      added the new path request parameter sync-id

    • breaking

      removed subschema #1 subschema #2 from the request body oneOf list

    • info

      added subschema #1 subschema #2 to the request body oneOf list