Schema record
@proseid v2026.06.19 EU

EU right-of-withdrawal record

Records an online consumer contract, the applicable national implementation, withdrawal window and exceptions, a consumer's withdrawal request, and the resulting refund obligation.

Compatible with
FormGuided assessmentDeterminationCompliance checklistAPI
Use Schema in a Flow
Publication
Protocol
Proseid_v1.0
Version
v2026.06.19
Applies in
European Union
Recommended language
English
Fields
25
Flow price
$0.20
Publisher fee
None
Standard base $0.20 · exact total is frozen when a Flow is created

Schema fields

25 fields
Required reimbursement issued
Boolean
Opt
The durable-medium acknowledgement included the withdrawal statement's content
Boolean
Opt
The consumer submitted this withdrawal through the online function
Boolean
Opt
Consumer was informed of the 14-day right before purchase
Boolean
Req
Online withdrawal submission date, time, and zone
String
Opt
The contract is within the Consumer Rights Directive withdrawal regime
Boolean
Req
Withdrawal requested by consumer
Boolean
Opt
The applicable Member State implementation has been checked
Boolean
Req
Article 16 exception
Select
Choices: None, Service fully performed after required consent and acknowledgement, Market dependent price, Bespoke or clearly personalised goods, Rapidly perishable goods, Sealed hygiene goods opened after delivery, Goods inseparably mixed after delivery, Qualifying alcoholic beverages with delayed delivery and market dependent value, Urgent repairs or maintenance specifically requested, Sealed audio video or software opened after delivery, Newspaper periodical or magazine except subscription, Public auction, Date specific non residential accommodation transport of goods car rental catering or leisure, Digital content started after required consent and acknowledgement, Other article 16 exception
Req
The trader offered to collect the goods
Boolean
Opt
Withdrawal acknowledgement sent without undue delay on a durable medium
Boolean
Opt
A prominent withdrawal function remained available throughout the withdrawal period
Boolean
Opt
Electronic destination for the withdrawal confirmation
String
Opt
Distance contract was concluded through an online interface
Boolean
Opt
Date withdrawal was requested
Date
Opt
Order reference
String
Req
The online statement had the required confirmation step
Boolean
Opt
Contract type
Select
Choices: Goods, Service, Digital content
Req
Delivery date (goods)
Date
Opt
Withdrawal was communicated within the applicable period
Boolean
Opt
Withdrawal track
String
Opt
Consumer name entered in the online withdrawal statement
String
Opt
Acknowledgement date, time, and zone
String
Opt
Contract date (services or non-tangible digital content)
Date
Opt
Goods returned or the consumer supplied evidence of return
Boolean
Opt

Example payload

JSON
{
  "responses": {
    "refund_issued": false,
    "durable_medium_acknowledgement_included_statement_content": false,
    "withdrawal_submitted_through_online_function": false,
    "consumer_informed_of_right": false,
    "online_withdrawal_submitted_at": "",
    "directive_scope_confirmed": false,
    "withdrawal_requested": false,
    "national_implementation_confirmed": false,
    "article_16_exception": "",
    "trader_offered_to_collect_goods": false,
    "durable_medium_acknowledgement_sent": false,
    "withdrawal_function_available": false,
    "online_withdrawal_confirmation_destination": "",
    "online_interface_contract": false,
    "withdrawal_request_date": "",
    "order_ref": "",
    "withdrawal_confirmation_step_available": false,
    "contract_type": "",
    "delivery_date": "",
    "withdrawal_within_applicable_period": false,
    "online_withdrawal_consumer_name": "",
    "durable_medium_acknowledgement_sent_at": "",
    "contract_date": "",
    "goods_returned_or_evidence_supplied": false
  },
  "effective_at": "2026-07-30"
}

The request body this schema expects. Fill in responses and keep the field IDs unchanged. Validation becomes callable after you use this release in a published Flow.

API usage

Create a Flow from this schema, then replace the route placeholders with that Flow's organization and address. Validation is free and runs against the exact release bound to the Flow. It returns the engine's resolved fields and legal time period when ready, or a structured error with field-level issues.

cURL
curl -X POST https://proseid.com/api/v1/validate/{your-org}/{flow-slug} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d @payload.json
200 OK
{
  "valid": true,
  "status": "READY",
  "definitions": { ... },
  "issues": [],
  "effective_at": "2026-07-19",
  "temporal_context": {
    "logic_version": "current",
    "valid_range": ["2026-01-01", null]
  }
}
422 Invalid
{
  "error": {
    "code": "validation_failed",
    "message": "the document did not pass validation",
    "details": {
      "status": "INCOMPLETE",
      "issues": [{
        "field_id": "refund_issued",
        "kind": "missing_required",
        "severity": "error",
        "trigger": "completion",
        "message": "Required field is missing"
      }]
    }
  }
}
A completed webhook also depends on the Flow's experience, signing, pricing, and delivery settings. Create a Flow with this schema, then use Send sample completion in its delivery settings to receive the full signed JSON without using your balance. Webhook guide

Published versions

Permanent, attributable versions
Loading published versions…

Trust ledger

Crowd → credentialed
P
Provenance
Community publisher (unverified)
@proseid · latest v2026.06.19
Community signal
0
0 votes

No votes yet.

Attestations · by version
0 total

No attestations yet. A verified professional can vouch for a specific version.

Discussion

0 comments
to join the discussion.