Skip to main content
Challenge

Build a Delegated Procurement Consent Receipt and Audit Verifier

Inspect automated agent transaction attempts against user consent receipts formatted with Beckn protocol context headers. Verify permission boundaries, cumulative budget limits, and category scopes to prevent unauthorized procurement actions.

Workflow AutomationHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Inspect automated agent transaction attempts against user consent receipts formatted with Beckn protocol context headers. Verify permission boundaries, cumulative budget limits, and category scopes to prevent unauthorized procurement actions.

Enterprise procurement auditor

Ingest incoming transaction callback payloads and extract Beckn protocol context fields including action, timestamp, and message parameters.

Compare requested transaction amounts and domain categories against the active cryptographic consent receipt parameters.

Detect permission overreaches such as expired timestamps, unauthorized seller IDs, or breached spend caps.

Output a tamper-evident audit disposition report approving or blocking the delegated transaction for human compliance sign-off.

Browser-based compliance dashboard showing side-by-side consent limits, agent execution traces, and audit logs.

Generate synthetic JSON fixtures conforming to Beckn protocol context and message formats with simulated delegation receipts. Starter examples below are synthetic. They are not downloaded records.

Beckn protocol specifications Applies Beckn protocol context and message packet structures (context fields like action, timestamp, domain) for verifying delegated transactions.

pydantic-ai, fastapi, pytest. Pydantic AI enforces type-safe schema validation on transaction contexts and structured consent audit decisions. Fast reasoning API or local 8B parameter instruction model capable of structured JSON output.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Rejects transactions when requested amount exceeds consent receipt spending cap.

Rejects actions when transaction timestamp exceeds consent validity horizon.

Emits compliant Beckn protocol ACK or NACK context structures for all simulated callbacks.

```json [ { "input": { "consent_receipt": { "receipt_id": "cr_101", "user_id": "usr_99", "max_amount_inr": 5000, "valid_until": "2025-12-31T23:59:59Z", "allowed_categories": [ "agriculture", "seeds" ] }, "transaction_packet": { "context": { "domain": "agriculture", "action": "confirm", "timestamp": "2025-06-15T10:00:00Z", "bap_id": "buyer-app.mock", "bpp_id": "coop-seller.mock" }, "message": { "order": { "id": "ord_552", "item_category": "seeds", "quote": { "price": { "value": 3400, "currency": "INR" } } } } } }, "expected_output": { "disposition": "APPROVED", "receipt_id": "cr_101", "violations": [], "ack_status": "ACK" } }, { "input": { "consent_receipt": { "receipt_id": "cr_102", "user_id": "usr_77", "max_amount_inr": 1500, "valid_until": "2025-01-01T00:00:00Z", "allowed_categories": [ "groceries" ] }, "transaction_packet": { "context": { "domain": "electronics", "action": "confirm", "timestamp": "2025-06-15T10:00:00Z", "bap_id": "buyer-app.mock", "bpp_id": "tech-seller.mock" }, "message": { "order": { "id": "ord_881", "item_category": "electronics", "quote": { "price": { "value": 2400, "currency": "INR" } } } } } }, "expected_output": { "disposition": "BLOCKED", "receipt_id": "cr_102", "violations": [ "Category 'electronics' not permitted in consent receipt", "Amount 2400 INR exceeds maximum authorized 1500 INR", "Transaction timestamp is past receipt validity" ], "ack_status": "NACK" } } ] ```

Simulates financial consent evaluations only; no real payments, bank credentials, or government IDs are handled. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Simulates financial consent evaluations only; no real payments, bank credentials, or government IDs are handled. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Rejects transactions when requested amount exceeds consent receipt spending cap. Rejects actions when transaction timestamp exceeds consent validity horizon. Emits compliant Beckn protocol ACK or NACK context structures for all simulated callbacks.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest incoming transaction callback payloads and extract Beckn protocol context fields including action, timestamp, and message parameters. Compare requested transaction amounts and domain categories against the active cryptographic consent receipt parameters. Detect permission overreaches such as expired timestamps, unauthorized seller IDs, or breached spend caps. Output a tamper-evident audit disposition report approving or blocking the delegated transaction for human compliance sign-off.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Rejects transactions when requested amount exceeds consent receipt spending cap. Rejects actions when transaction timestamp exceeds consent validity horizon. Emits compliant Beckn protocol ACK or NACK context structures for all simulated callbacks.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Browser-based compliance dashboard showing side-by-side consent limits, agent execution traces, and audit logs.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Simulates financial consent evaluations only; no real payments, bank credentials, or government IDs are handled.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest incoming transaction callback payloads and extract Beckn protocol context fields including action, timestamp, and message parameters.

  • Compare requested transaction amounts and domain categories against the active cryptographic consent receipt parameters.

  • Detect permission overreaches such as expired timestamps, unauthorized seller IDs, or breached spend caps.

  • Output a tamper-evident audit disposition report approving or blocking the delegated transaction for human compliance sign-off.

Resources and assets

Reference links and supporting material

Dataset notes

Generate synthetic JSON fixtures conforming to Beckn protocol context and message formats with simulated delegation receipts. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Pydantic AI

Typed Python agent framework.

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest incoming transaction callback payloads and extract Beckn protocol context fields including action, t...
  • Rejects transactions when requested amount exceeds consent receipt spending cap. Rejects actions when trans...
  • Browser-based compliance dashboard showing side-by-side consent limits, agent execution traces, and audit l...
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 2 configured tools

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • Pydantic AI · Optional
Orchestration
  • Pydantic AI · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Delegated Procurement Consent Receipt and Audit Verifier