get-kyc-webhook-PROVIDER_NAME-star.rst (1192B)
1 .. http:get:: /kyc-webhook/$PROVIDER_NAME/* 2 .. http:post:: /kyc-webhook/$PROVIDER_NAME/* 3 .. http:get:: /kyc-webhook/$LOGIC/* 4 .. http:post:: /kyc-webhook/$LOGIC/* 5 6 All of the above endpoints can be used to update KYC status of a particular 7 payment target. They provide information to the KYC logic of the exchange 8 that allows it to verify that the user has completed the KYC process. May 9 be a GET or a POST request, depending on the specific "$LOGIC" and/or the 10 "$PROVIDER_NAME". 11 12 **Request:** 13 14 Details on the request depend on the specific KYC logic 15 that was used. 16 17 **Response:** 18 19 :http:statuscode:`204 No content`: 20 The operation succeeded. 21 :http:statuscode:`404 Not found`: 22 The specified logic is unknown. 23 This response comes with a standard `ErrorDetail` response with 24 a code of ``TALER_EC_EXCHANGE_KYC_GENERIC_LOGIC_UNKNOWN``. 25 :http:statuscode:`500 Internal Server Error`: 26 The server experienced an internal error. 27 This response comes with a standard `ErrorDetail` response with 28 a code of ``TALER_EC_GENERIC_INTERNAL_INVARIANT_FAILURE``, 29 ``TALER_EC_GENERIC_DB_STORE_FAILED``, or 30 ``TALER_EC_EXCHANGE_GENERIC_BAD_CONFIGURATION``.