Nopan

Nopan Webhooks API

API of the webhooks notifications Nopan will send if configured in the portal.

GitHub OpenAPI

Operations 4

POST /notifications/paymentInitiate Payment initiate notification #
POST /notifications/paymentFinalize Payment finalize notification #
POST /notifications/paymentCapture Payment capture notification #
POST /notifications/paymentRefund Payment refund notification #

Documentation

📖
Authentication
https://artifacts.apis.io/nopan/authentication/nopan-authentication.yml

Specifications

⚙
OpenAPI
https://artifacts.apis.io/nopan/openapi/nopan-webhooks-api-openapi.yml

Other Resources

🔗
OAuthScopes
https://artifacts.apis.io/nopan/scopes/nopan-scopes.yml
🔗
Conventions
https://artifacts.apis.io/nopan/conventions/nopan-conventions.yml
🔗
ErrorCatalog
https://artifacts.apis.io/nopan/errors/nopan-error-codes.yml
🔗
Webhooks
https://artifacts.apis.io/nopan/asyncapi/nopan-webhooks.yml
🔗
Sandbox
https://artifacts.apis.io/nopan/sandbox/nopan-sandbox.yml
🔗
DataModel
https://artifacts.apis.io/nopan/data-model/nopan-data-model.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/nopan:nopan-webhooks-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

nopan-webhooks-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  version: v1
  title: Nopan Webhooks API
  description: 'Download Nopan Postman collection: Download'
servers:
- url: https://api.nopan.io
tags:
- name: Webhooks
  description: API of the webhooks notifications Nopan will send if configured in the portal.
paths:
  /notifications/paymentInitiate:
    post:
      tags:
      - Webhooks
      operationId: initiateNotification
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                notificationId:
                  type: string
                  format: uuid
                  description: 'Unique id of the notification.<br/><small>Example: <i>56562de8-9b89-4628-b2fe-cd1b2cc1e95b</i></small>'
                transactionId:
                  type: string
                  description: 'Nopan''s transaction ID<br/><small>Example: <i>ee2anef9bt</i></small>'
                clientTransactionId:
                  type: string
                  description: 'The unique client''s internal transaction ID<br/><small>Example: <i>order11234</i></small>'
                status:
                  type: string
                  description: The current state of the transaction
                statusInfo:
                  type: object
                  properties:
                    reasonCode:
                      type: string
                    message:
                      type: string
                  description: The information about the status of the request
                notificationType:
                  type: string
                  enum:
                  - PAYMENT_INITIATE
                  - PAYMENT_FINALIZE
                  - PAYMENT_CAPTURE
                  - PAYMENT_REFUND
              additionalProperties: false
            examples:
              Initiated:
                summary: Payment initiate notification
                description: Initiate information including status, etc
                value:
                  notificationId: fc5adbcd-5f08-4d09-9307-08d950809f0d
                  transactionId: p9vhkuj92yav
                  clientTransactionId: client-txn-54c8c9bc
                  status: PENDING
                  statusInfo:
                    reasonCode: '-1'
                    message: OK
                  notificationType: PAYMENT_INITIATE
        required: true
      responses:
        '200':
          description: OK
      summary: Payment initiate notification
      description: Notifies you about updates on initiate. The exact path of the request is configured through our portal.
  /notifications/paymentFinalize:
    post:
      tags:
      - Webhooks
      operationId: finalizedNotification
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                notificationId:
                  type: string
                  format: uuid
                  description: 'Unique id of the notification.<br/><small>Example: <i>56562de8-9b89-4628-b2fe-cd1b2cc1e95b</i></small>'
                transactionId:
                  type: string
                  description: 'Nopan''s transaction ID<br/><small>Example: <i>ee2anef9bt</i></small>'
                clientTransactionId:
                  type: string
                  description: 'The unique client''s internal transaction ID<br/><small>Example: <i>order11234</i></small>'
                payerDetails:
                  type: object
                  properties:
                    paymentToken:
                      type: string
                      description: 'The payment token of the payer<br/><small>Example: <i>eyJraWQiOiI5MDU5OGE2NC1jZWNlLTQ1YzItOGUzMy02OTAzODA5OTBlYjgiLCJhbGciOiJSUzI1NiJ9...</i></small>'
                  description: Payer identity information
                status:
                  type: string
                  description: The current state of the transaction
                statusInfo:
                  type: object
                  properties:
                    reasonCode:
                      type: string
                    message:
                      type: string
                  description: The information about the status of the request
                notificationType:
                  type: string
                  enum:
                  - PAYMENT_INITIATE
                  - PAYMENT_FINALIZE
                  - PAYMENT_CAPTURE
                  - PAYMENT_REFUND
              additionalProperties: false
            examples:
              Finalized:
                summary: Payment finalize notification
                description: Finalize information including status, etc.
                value:
                  notificationId: fc5adbcd-5f08-4d09-9307-08d950809f0d
                  transactionId: p9vhkuj92yav
                  clientTransactionId: client-txn-54c8c9bc
                  status: APPROVED
                  statusInfo:
                    reasonCode: '-1'
                    message: OK
                  notificationType: PAYMENT_FINALIZE
        required: true
      responses:
        '200':
          description: OK
      summary: Payment finalize notification
      description: Notifies you about updates on finalize. The exact path of the request is configured through our portal.
  /notifications/paymentCapture:
    post:
      tags:
      - Webhooks
      operationId: captureNotification
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                notificationId:
                  type: string
                  format: uuid
                  description: 'Unique id of the notification.<br/><small>Example: <i>56562de8-9b89-4628-b2fe-cd1b2cc1e95b</i></small>'
                transactionId:
                  type: string
                  description: 'Nopan''s transaction ID<br/><small>Example: <i>ee2anef9bt</i></small>'
                clientTransactionId:
                  type: string
                  description: 'The unique client''s internal transaction ID<br/><small>Example: <i>order11234</i></small>'
                amount:
                  type: integer
                  format: int64
                capturedAmount:
                  type: integer
                  format: int64
                status:
                  type: string
                  description: The current state of the transaction
                statusInfo:
                  type: object
                  properties:
                    reasonCode:
                      type: string
                    message:
                      type: string
                  description: The information about the status of the request
                notificationType:
                  type: string
                  enum:
                  - PAYMENT_INITIATE
                  - PAYMENT_FINALIZE
                  - PAYMENT_CAPTURE
                  - PAYMENT_REFUND
              additionalProperties: false
            examples:
              Capture:
                summary: Payment capture notification
                description: Capture information including amount, status, etc.
                value:
                  notificationId: fc5adbcd-5f08-4d09-9307-08d950809f0d
                  transactionId: p9vhkuj92yav
                  clientTransactionId: client-txn-54c8c9bc
                  amount: 1000
                  capturedAmount: 1000
                  status: APPROVED
                  statusInfo:
                    reasonCode: '-1'
                    message: OK
                  notificationType: PAYMENT_CAPTURE
        required: true
      responses:
        '200':
          description: OK
      summary: Payment capture notification
      description: Notifies you about updates on capture. The exact path of the request is configured through our portal.
  /notifications/paymentRefund:
    post:
      tags:
      - Webhooks
      operationId: refundNotification
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                notificationId:
                  type: string
                  format: uuid
                  description: 'Unique id of the notification.<br/><small>Example: <i>56562de8-9b89-4628-b2fe-cd1b2cc1e95b</i></small>'
                transactionId:
                  type: string
                  description: 'Nopan''s transaction ID<br/><small>Example: <i>ee2anef9bt</i></small>'
                clientTransactionId:
                  type: string
                  description: 'The unique client''s internal transaction ID<br/><small>Example: <i>order11234</i></small>'
                amount:
                  type: integer
                  format: int64
                refundedAmount:
                  type: integer
                  format: int64
                status:
                  type: string
                  description: The current state of the transaction
                statusInfo:
                  type: object
                  properties:
                    reasonCode:
                      type: string
                    message:
                      type: string
                  description: The information about the status of the request
                notificationType:
                  type: string
                  enum:
                  - PAYMENT_INITIATE
                  - PAYMENT_FINALIZE
                  - PAYMENT_CAPTURE
                  - PAYMENT_REFUND
              additionalProperties: false
            examples:
              Refund:
                summary: Payment refunded notification
                description: Refund information including amount, status, etc.
                value:
                  notificationId: fc5adbcd-5f08-4d09-9307-08d950809f0d
                  transactionId: p9vhkuj92yav
                  clientTransactionId: client-txn-54c8c9bc
                  amount: 1000
                  refundedAmount: 1000
                  status: APPROVED
                  statusInfo:
                    reasonCode: '-1'
                    message: OK
                  notificationType: PAYMENT_REFUND
        required: true
      responses:
        '200':
          description: OK
      summary: Payment refund notification
      description: Notifies you about updates on refund. The exact path of the request is configured through our portal.