@enfuce/nextgen-sdk 0.0.1

package/dist/esm/threeds-oob/index.js

@@ -0,0 +1,15 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * 3DS OOB Outgoing Webhook API
+ * The 3DS Authentication API supports OOB (out of band) authentication during 3DS payment processing, where the client\'s own cardholder authentication service is used.  All endpoints use HTTP response codes; requests and responses are UTF-8 encoded in JSON format. A client must be able to handle new elements added to either the request or response without breaking.   **Timeout**: The 3rd party authentication system has 150 seconds (default, configurable during 3DS setup) to send a callback with the authentication challenge result. After this, Enfuce responds with a timeout to ACS and end user authentication fails.  **CustomerNumber** in this context is equal to `cardholder.customerNumber` in other parts of the Enfuce API.  ## 3DS OOB Authentication flow  ```   Payment Network          Enfuce 3DS API                            Client System          |                       |                                          |          |-- 3ds auth request -->|                                          |  (1)          |                       |-- POST /v1/3ds/oob/challenge/initiate  ->|  (2)          |                       |<-------------- HTTP 200 OK --------------|  (3)          |                       |                                          |          |                       |                               authenticate cardholder          |                       |                                          |          |                       |<-- POST /v1/3ds/challenge/oob/result  ---|  (4)          |<- 3ds auth response --|                                          |  (5) ```  1. Enfuce receives a 3DS authentication request from the payment network including merchant information. 2. Enfuce calls the client system, requesting a cardholder authentication.    - The request contains both `authenticationId` and `challengeId` (UUIDs) that the client system uses when sending the challenge result back.    - It also contains the customerNumber and other contextual info. 3. The client system must return an HTTP 200 OK response within 2 seconds. 4. Once the client system has a result from the cardholder authentication, it calls the \"Submit authentication challenge result\" endpoint,    which needs to happen within 150 seconds from the start. 5. Enfuce responds to the payment network, and the authorization process can proceed.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+export * from "./api";
+export * from "./configuration";