QWqwist
Strong Customer Authentication

Solve payment 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.

post/rest/payments/{payment-id}/init/{init-id}/challenges/{challenge-id}/response

Request

Parameters

#/paths/~1rest~1payments~1{payment-id}~1init/post/parameters/0 (unresolved $ref)
#/paths/~1rest~1payments~1{payment-id}~1init~1{init-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

0 required(unresolved $ref)
OR
1 required(unresolved $ref)
OR
2 required(unresolved $ref)
OR
3 required(unresolved $ref)

Response

(unresolved $ref)

Changes

  • 398592d93b1fRevision changes
    • breaking

      added the new path request parameter challenge-id

    • breaking

      added the new path request parameter init-id

    • breaking

      added the new path request parameter payment-id

    • breaking

      removed from the request body oneOf list

    • info

      added to the request body oneOf list

    • info

      added the media type application/json for the response with the status