Library

Transaction enrichment library for PHP

Use TxnKit as a transaction enrichment API from PHP. This page shows the safe request shape, a short code snippet, and the boundary for keeping sensitive data out of the integration.

Ask about a 100-descriptor cleanup auditInspect the API

Target intent

PHP developers adding transaction enrichment through a direct API request.

TxnKit does not add a payment gateway, reconciliation, or charge lookup workflow.

Raw descriptor

PAYPAL *ACME-SUPPLY

Short PHP API snippet

$ch = curl_init("https://api.txnkit.dev/v1/enrich");
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_HTTPHEADER => [
        "Authorization: Bearer " . getenv("TXNKIT_API_KEY"),
        "Content-Type: application/json"
    ],
    CURLOPT_POSTFIELDS => json_encode(["raw_description" => "PAYPAL *ACME-SUPPLY", "country" => "CA"]),
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_TIMEOUT_MS => 1000
]);

Keep API keys out of browser bundles. For frontend stacks, call a backend route or serverless function that owns the TxnKit request.

API-shaped output

{
  "normalized_merchant": "acme supply",
  "display_name": "Acme Supply",
  "category": null,
  "subcategory": null,
  "website": null,
  "logos": {
    "preferred": null,
    "variants": [],
    "warnings": [
      "no_verified_logo_for_local_merchant"
    ]
  },
  "confidence": 0.56,
  "recurring_hint": false,
  "processor_hint": "paypal",
  "location_hint": null,
  "signals": [
    "applied_processor_paypal_star"
  ],
  "warnings": [
    "local_merchant_identity_not_verified"
  ]
}

Low-confidence results should keep fallback labels and warnings visible instead of forcing a guessed logo or website.

When to use

  • You are building in PHP and need one-descriptor merchant cleanup through an HTTP API.
  • Your app can keep the TxnKit API key on the server side or inside a trusted serverless function.
  • You need merchant display names, categories, confidence, signals, warnings, and logo-ready metadata.

When not to use

  • TxnKit does not add a payment gateway, reconciliation, or charge lookup workflow.
  • Do not use TxnKit to process card numbers, account numbers, full statements, bank credentials, emails, phone numbers, addresses, customer names, or customer PII.
  • Do not use TxnKit when the product requirement is guaranteed merchant identity, every-merchant resolution, or contracted uptime terms.

Proof surfaces

The public contract is POST /v1/enrich, backed by the OpenAPI file, benchmark examples, privacy rules, and deterministic request-path tests.

OpenAPI · Benchmark · Security · Pricing

Related pages