openapi: 3.2.0 info: version: v1 title: Weavr Embedded Payment Run Authentication Factors Webhooks API license: name: private url: https://weavr.io x-logo: url: https://weavr-cdn.s3.eu-central-1.amazonaws.com/weavr-payment-run-logo.png backgroundColor: '#FFFFFF' altText: Weavr description: "Weavr Payment Run Plug-in API provides a simple and flexible way for Embedders to add payment execution capabilities in their application.\n\nBy integrating Weavr Payment Run plug-in API in your application, you can embed banking and payment capabilities within your app to boost productivity for your users in a seamless experience.\n\n# Authentication\nEach request to the API must include an `api_key` that represents your account. You can obtain an API Key by registering for a Embedder account [here](https://portal.weavr.io/register/?plugin=payment-run).\n\nAlmost all endpoints require a secondary authentication token `auth_token` that represents the user for whom the request is being executed.\n\n# Postman Collection\nTo help you get started with your integration, you can download the [Postman](https://postman.com) collection [here](https://sandbox.weavr.io/payment-run/v1/postman). The collection includes the steps you’ll need to follow to integrate Embedded Payment Run within your app. \n\nThe collection makes use of environment variables to pre-fill details associated with your Sandbox account, such as your account’s API Key. You can download your Sandbox Account environment file from the [Sandbox Portal](https://portal.weavr.io/register/?plugin=payment-run).\n" servers: - url: https://sandbox.weavr.io/payment-run description: Sandbox security: - apiKey: [] authToken: [] tags: - name: Authentication Factors Webhooks description: Notification of the Authentication Factors that are used for the `Identity`. x-displayName: Authentication Factors paths: {} webhooks: authenticationFactorsWatch: post: summary: Enrolment status description: Notification that an enrolment has been accepted or declined. operationId: authentication_factors_watch tags: - Authentication Factors Webhooks security: [] parameters: - name: call-ref in: header description: 'A call reference generated by the caller and unique to the caller to provide correlation between the caller and system with a maximum length of 255 ' required: false style: simple explode: false schema: type: string - name: published-timestamp in: header description: The timestamp, expressed in Epoch timestamp using millisecond precision, when this event was published. required: true style: simple explode: false schema: type: integer format: int64 - name: signature in: header description: The signature to verify the authenticity of this request. This is the base64 hash (HmacSHA256) of the `published-timestamp` using your API key. required: true style: simple explode: false schema: type: string - name: signature-v2 in: header description: The signature to verify the authenticity of this request. This is the base64 hash (HmacSHA256) of the `call-ref` header, the request body, and the `published-timestamp` header, all concatenated without spaces, and signed using your API key. required: true style: simple explode: false schema: type: string requestBody: content: application/json: schema: type: object properties: type: type: string enum: - authenticationFactorsWatch payload: required: - credentialId - publishedTimestamp - status - type type: object properties: credential: required: - type - id type: object properties: type: maxLength: 50 pattern: ^[a-zA-Z0-9_-]+$ type: string enum: - ROOT - USER description: The type of user. id: type: string pattern: ^[0-9]+$ description: The identifier of the user. type: type: string status: type: string enum: - ACTIVE - INACTIVE publishedTimestamp: type: string pattern: ^[0-9]+$ description: Epoch timestamp using millisecond precision. required: true responses: '200': description: Return a 200 status to indicate that the data was received successfully components: securitySchemes: apiKey: name: api-key type: apiKey in: header description: The API Key representing your Weavr account. You can find your API Key in your Weavr Portal in the API Credentials page. authToken: type: http description: The authentication token representing the user. This will be included in the login response object. scheme: bearer bearerFormat: JWT x-tagGroups: - name: Authentication tags: - Tokens - Passwords - name: Authorisation tags: - Additional Factors - Step up - name: Identities tags: - Buyers - Buyer Authorised Users - name: Payment runs tags: - Payment runs - name: Instruments tags: - Linked Accounts - name: Institutions tags: - Institutions - name: Simulators tags: - Simulator - name: Events tags: - Buyers Webhooks - Payment runs Webhooks - Linked Accounts Webhooks - Tokens Webhooks - Stepup Webhooks - Authentication Factors Webhooks - Transactions Webhooks