Depay · Schema

PostPaymentsDepayCallbackRequest

CompanyPaymentsCryptoWeb3FinTechAPI

Properties

Name	Type	Description
status	string	Status of the payment (e.g., 'success')
failed_reason	string	Reason for failure if applicable
blockchain	string	Blockchain network used for the transaction
transaction	string	Transaction hash
sender	string	Sender's wallet address
nonce	string	Transaction nonce
receiver	string	Receiver's wallet address
token	string	Token address
decimals	integer	Token decimals
commitment	string	Confirmation level (e.g., 'confirmed' or 'finalized')
confirmations	integer	Number of block confirmations
after_block	string	Block number after which transaction occurred
amount	string	Payment amount
fee_amount	string	Fee amount if applicable
fee_receiver	string	Fee receiver address if applicable
payload	object	Collected payment data and injected payload data
secret_id	string	Unique secret identifier for the callback
callback	string	Callback URL
release	boolean	Release status
forward_to	string	URL to forward the request to
forward_on_failure	boolean	Whether to forward on failure
confirmed_at	string	ISO 8601 timestamp when payment was confirmed
created_at	string	ISO 8601 timestamp when callback was created
updated_at	string	ISO 8601 timestamp when callback was last updated

View JSON Schema on GitHub

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/depayapp-com/json-schema/depayapp-com-post-payments-depay-callback-request-schema.json",
  "title": "PostPaymentsDepayCallbackRequest",
  "x-generated": "2026-10-29",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/_ae-authored/depayapp-com-openapi-generated.yml#/components/schemas/PostPaymentsDepayCallbackRequest",
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "Status of the payment (e.g., 'success')"
    },
    "failed_reason": {
      "type": "string",
      "description": "Reason for failure if applicable"
    },
    "blockchain": {
      "type": "string",
      "description": "Blockchain network used for the transaction"
    },
    "transaction": {
      "type": "string",
      "description": "Transaction hash"
    },
    "sender": {
      "type": "string",
      "description": "Sender's wallet address"
    },
    "nonce": {
      "type": "string",
      "description": "Transaction nonce"
    },
    "receiver": {
      "type": "string",
      "description": "Receiver's wallet address"
    },
    "token": {
      "type": "string",
      "description": "Token address"
    },
    "decimals": {
      "type": "integer",
      "description": "Token decimals"
    },
    "commitment": {
      "type": "string",
      "description": "Confirmation level (e.g., 'confirmed' or 'finalized')"
    },
    "confirmations": {
      "type": "integer",
      "description": "Number of block confirmations"
    },
    "after_block": {
      "type": "string",
      "description": "Block number after which transaction occurred"
    },
    "amount": {
      "type": "string",
      "description": "Payment amount"
    },
    "fee_amount": {
      "type": "string",
      "description": "Fee amount if applicable"
    },
    "fee_receiver": {
      "type": "string",
      "description": "Fee receiver address if applicable"
    },
    "payload": {
      "type": "object",
      "description": "Collected payment data and injected payload data"
    },
    "secret_id": {
      "type": "string",
      "description": "Unique secret identifier for the callback"
    },
    "callback": {
      "type": "string",
      "description": "Callback URL"
    },
    "release": {
      "type": "boolean",
      "description": "Release status"
    },
    "forward_to": {
      "type": "string",
      "description": "URL to forward the request to"
    },
    "forward_on_failure": {
      "type": "boolean",
      "description": "Whether to forward on failure"
    },
    "confirmed_at": {
      "type": "string",
      "description": "ISO 8601 timestamp when payment was confirmed"
    },
    "created_at": {
      "type": "string",
      "description": "ISO 8601 timestamp when callback was created"
    },
    "updated_at": {
      "type": "string",
      "description": "ISO 8601 timestamp when callback was last updated"
    }
  },
  "required": [
    "status",
    "blockchain",
    "transaction",
    "sender",
    "receiver",
    "token",
    "decimals",
    "commitment",
    "confirmations",
    "amount",
    "secret_id",
    "callback"
  ]
}

Work with this as data

Every JSON Schema 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 schemas

4 MCP tools reach this

find_json_schemasBrowse and filter every JSON Schema in the catalog.
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 JSON Schema

curl "https://apis.io/api/v1/json-schemas/depayapp-com-post-payments-depay-callback-request"

All schemas

curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.