HomePassportVerify AgentAcceptance Checkx402 SandboxAgentic financeRegistry
Public proof · Agentic finance acceptance

Crossmint can let the agent pay. Concordium can help the service say yes.

Crossmint is building payment infrastructure for agentic finance: wallets, cards, x402-style requests, and orchestration that let agents buy, sell, and pay. Gregers adds the acceptance check around that moment: before a merchant, API, or service responds, it can inspect who stands behind the agent, what authority applies, what limit was used, and what proof remains after payment.

Gregers public proof only: not a Crossmint partnership claim, not a Mastercard partnership claim, not official Concordium/Foundation output, and staging/testnet payment evidence only.

Open the proof loopAgent Card JSONVerifier examples
What becomes possible
Verified agents can buy data, call APIs, book services and leave a useful receipt.

Payment alone says value moved. Agent verification helps the counterparty decide whether this autonomous request should be accepted.

Target use case

agentic payment request + Concordium accountable-agent proof before the resource is released. Works as a wrapper around card, wallet, x402, or API-payment moments.

Who receives and decides?

Recipient/acceptor: the API, merchant, or service receiving the agentic payment request. For this proof, Crossmint-style staging wallet/payment evidence covers the payment-rail side; the service can use Gregers/Concordium evidence to decide whether to release the resource.

Proof loop

1. Discover
agent card + wallet rail
2. Request
payment terms + authority context
3. Verify
Agent #40 + authority hash
4. Pay
staging/testnet evidence
5. Receipt
signed proof after action
Live machine-readable evidence
loading…
Open signed receiptOpen payment confirmation
Status
Public proof page

No production payment is executed by this page.

Proof JSON
The proof JSON will appear here.

Fast read for Crossmint-style teams

One-sentence thesis

Payment infrastructure answers whether an agent can pay. Gregers/Concordium helps the merchant decide whether the agent should be accepted.

Use this link for

Explaining the acceptance layer around agentic cards, wallets, x402-style paid APIs, and delegated agent spend.

Machine-readable handoff

Start with the Agent Card and status JSON, then inspect the signed receipt and payment-confirmation proof.

Status JSONAgent Card
What we need Crossmint to validate

Pick the integration point: Agent Card extension, x402/payment metadata, Verifiable Credential claim, merchant/API webhook payload, or another Crossmint-preferred field. Gregers can adapt the proof to that shape.

What the service can check before release

Agent identity, owner/authority context, payment-request binding, wallet-control evidence, staging payment evidence, receipt hash, and explicit production boundaries.

What is live, and what is not claimed

Agentic finance pattern

Payment networks and wallet rails can make it possible for agents to transact. The merchant-side question is acceptance: should this autonomous request be served, under whose authority, with what cap, and with what proof after payment?

Live evidence

Gregers exposes an Agent Card, x402-shaped challenge data, signed receipts, verification examples, and a read-only Base Sepolia payment confirmation endpoint.

Staging payment evidence

The Crossmint/USDXM payment evidence is testnet/staging evidence. It is useful proof of shape, not production payment authority.

Concordium role

Concordium is used for accountable-agent identity and verification. It is not presented as the payment rail in this proof.

Boundary

This is a Gregers public proof page. It is not a Crossmint partnership claim and not a Mastercard partnership claim and not official Concordium/Foundation output. It publishes no raw personal ID data, Crossmint API keys, signer secrets, KYC data, recovery material, bank/card details, or production funds. No new payment, credential issuance, revocation, or Concordium transaction is triggered by opening this page.