For API, agent & business platforms

Connect the purchase.
Account for the result.

Bring order, payment and delivery records into one explainable reconciliation workflow. Start with a scoped, read-only integration pilot.

Discuss a paid pilotInspect the demo

Your existing payment provider stays in place. No funds move through this pilot.

Start without moving moneyRead-only records; no wallet keys or spending authority.
Keep unknown outcomes visibleMissing delivery stays incomplete. It is not a refund.
Make results inspectableDeterministic checks and explicit issue codes.

One workflow. An agreed acceptance test.

A paid pilot with a defined finish line.

For platforms already handling paid API credits, structured data purchases or similar transactions. We agree the evidence sources and measurable acceptance criteria before starting.

Proposed platform pilot

$5,000 one-off, subject to a written scope

  • One commercial workflow and agreed JSON export mappings.
  • Up to 100 consented example purchases, with sensitive fields removed.
  • A reproducible exception report and customer-approved acceptance fixtures.
  • Measured integration effort and a recommendation for ongoing operation.

Indicative four-week delivery window after data access and scope agreement. Final fees, applicable taxes, responsibilities and delivery dates are confirmed in writing. No automatic renewal or payment collection from this page.

Acceptance, not an open-ended build

The pilot must show its work.

  • Match order IDs, named recipients, currencies and integer amounts.
  • Flag duplicate references, missing evidence and quantity discrepancies.
  • Explain late delivery against the supplied deadline.
  • Replay the same input to obtain the same report.

Third-party signatures, chain finality, beneficiary ownership and physical-world delivery require separate verification. This pilot does not execute payments, guarantee fraud prevention, provide insurance or certify regulatory compliance.

Synthetic examples · computed by the reconciliation module

Three outcomes. Nothing hidden.

These fixed demonstration inputs are processed by the same pure reconciliation function used by the local pilot runner. They contain no real customer activity. Open a report to inspect the exact scope and limitations.

Records agree

matched

The supplied order, payment and delivered units match.

Inspect the input and computed report

Supplied example

{
  "order": {
    "orderId": "demo-order-001",
    "payeeId": "demo-vendor-001",
    "currency": "USD",
    "amountMinor": "5000",
    "units": "100",
    "unitCode": "API_CALL",
    "approvedAtMs": 1750000000000,
    "deliveryDueAtMs": 1750003600000
  },
  "payments": [
    {
      "reference": "demo-payment-001",
      "orderId": "demo-order-001",
      "payeeId": "demo-vendor-001",
      "currency": "USD",
      "amountMinor": "5000",
      "settledAtMs": 1750000060000
    }
  ],
  "deliveries": [
    {
      "reference": "demo-delivery-001",
      "orderId": "demo-order-001",
      "payeeId": "demo-vendor-001",
      "units": "100",
      "unitCode": "API_CALL",
      "deliveredAtMs": 1750000120000
    }
  ]
}

Computed report

{
  "schemaVersion": "1",
  "scope": "supplied-data-consistency-only",
  "limitations": [
    "Supplied approval, identity, ownership, settlement and delivery claims are not independently verified.",
    "Duplicate detection covers only the supplied arrays, not other requests or external systems.",
    "Currency labels, minor-unit conventions, reference namespaces and unit definitions must be agreed by the caller.",
    "No funds are moved, held, reversed or refunded; matched is not a security, legal or delivery-quality guarantee."
  ],
  "status": "matched",
  "orderId": "demo-order-001",
  "totals": {
    "paidAmountMinor": "5000",
    "deliveredUnits": "100"
  },
  "issues": []
}

Delivery evidence missing

incomplete

Payment is recorded; delivery is unknown. No refund is inferred.

Inspect the input and computed report

Supplied example

{
  "order": {
    "orderId": "demo-order-001",
    "payeeId": "demo-vendor-001",
    "currency": "USD",
    "amountMinor": "5000",
    "units": "100",
    "unitCode": "API_CALL",
    "approvedAtMs": 1750000000000,
    "deliveryDueAtMs": 1750003600000
  },
  "payments": [
    {
      "reference": "demo-payment-001",
      "orderId": "demo-order-001",
      "payeeId": "demo-vendor-001",
      "currency": "USD",
      "amountMinor": "5000",
      "settledAtMs": 1750000060000
    }
  ],
  "deliveries": []
}

Computed report

{
  "schemaVersion": "1",
  "scope": "supplied-data-consistency-only",
  "limitations": [
    "Supplied approval, identity, ownership, settlement and delivery claims are not independently verified.",
    "Duplicate detection covers only the supplied arrays, not other requests or external systems.",
    "Currency labels, minor-unit conventions, reference namespaces and unit definitions must be agreed by the caller.",
    "No funds are moved, held, reversed or refunded; matched is not a security, legal or delivery-quality guarantee."
  ],
  "status": "incomplete",
  "orderId": "demo-order-001",
  "totals": {
    "paidAmountMinor": "5000",
    "deliveredUnits": "0"
  },
  "issues": [
    {
      "code": "MISSING_DELIVERY",
      "path": "deliveries"
    }
  ]
}

Recipient mismatch

mismatch

The supplied payment names a different recipient from the order.

Inspect the input and computed report

Supplied example

{
  "order": {
    "orderId": "demo-order-001",
    "payeeId": "demo-vendor-001",
    "currency": "USD",
    "amountMinor": "5000",
    "units": "100",
    "unitCode": "API_CALL",
    "approvedAtMs": 1750000000000,
    "deliveryDueAtMs": 1750003600000
  },
  "payments": [
    {
      "reference": "demo-payment-001",
      "orderId": "demo-order-001",
      "payeeId": "demo-other-vendor",
      "currency": "USD",
      "amountMinor": "5000",
      "settledAtMs": 1750000060000
    }
  ],
  "deliveries": [
    {
      "reference": "demo-delivery-001",
      "orderId": "demo-order-001",
      "payeeId": "demo-vendor-001",
      "units": "100",
      "unitCode": "API_CALL",
      "deliveredAtMs": 1750000120000
    }
  ]
}

Computed report

{
  "schemaVersion": "1",
  "scope": "supplied-data-consistency-only",
  "limitations": [
    "Supplied approval, identity, ownership, settlement and delivery claims are not independently verified.",
    "Duplicate detection covers only the supplied arrays, not other requests or external systems.",
    "Currency labels, minor-unit conventions, reference namespaces and unit definitions must be agreed by the caller.",
    "No funds are moved, held, reversed or refunded; matched is not a security, legal or delivery-quality guarantee."
  ],
  "status": "mismatch",
  "orderId": "demo-order-001",
  "totals": {
    "paidAmountMinor": "0",
    "deliveredUnits": "100"
  },
  "issues": [
    {
      "code": "PAYMENT_PAYEE_MISMATCH",
      "path": "payments[0].payeeId"
    },
    {
      "code": "UNDERPAYMENT",
      "path": "payments"
    }
  ]
}

The demo makes no network calls and cannot establish that the supplied evidence is authentic. A production integration requires authorised data sources, access controls and an agreed verification policy.

One platform direction. Your existing building blocks.

Keep the wider catalogue connected.

Explore the existing HCRB / code402.dev surfaces. A catalogue listing is not a guarantee of live capacity, coverage or partner availability; confirm each service's scope and current terms before purchase.

Invoices & records

Connect business references to an agreed payment workflow. Confirm all fees in the actual quote.

Compute catalogue

Provider capacity, fulfilment and pricing must be confirmed before any order.

Studio workflows

Specialist service requirements are scoped separately from the reconciliation pilot.

Bring one real workflow.

Tell us which systems need to agree, where exceptions happen, and who owns the process. Start with a description—not credentials, payment details or customer records.

Email the pilot brief

This link opens your email client. Nothing is submitted automatically. Existing support address: ops@hcrb.in. Please use the linked privacy notice before sharing personal information.