Conditional payments also need a dispute and refund procedure
Paying when an agreed condition is met sounds simple. A company and its customer also need to know who confirms fulfilment, what happens in a dispute and how money is returned after a completed payment. These rules belong in the design from the start.
Take the full article to your ChatGPT, Claude or Gemini and explore what it means for your work.
Tokenizace.cz Editorial Team · Planned publication: 2026-11-20 · Sources checked as of: 2026-11-01
Basis of the article: This article draws on the primary material below, checked as of 1 November 2026. Sources 1–3 provide the initial subject basis; further references add professional and comparative context. The practical approach and illustrative situations are editorial analysis, not test results reported by the named institutions.
Reader summary
- ECB includes conditional payments in research and experimentation.
- The condition concerns payment execution rather than restricting later money use.
- Consent, fulfilment and confirmed outcomes need their own evidence.
What is being explored for the digital euro
ECB’s September call includes conditional payments and distinguishes them from money with restricted uses. A potential digital euro issuance decision follows adoption of the relevant legislation. [1] This is a research framework rather than a finished service for our example.
The innovation platform separates experimentation with features from exploration of further opportunities. [2] Earlier findings help frame questions. [3] The scenario below is an editorial design, not a claim about available interfaces, an approved product or selection outcomes after 1 November.
One delivery and a precise condition
A fictional small business supplies equipment to a customer. They want an authorised payment released after acceptance. The requirement must identify who confirms acceptance, what exactly is confirmed and which order version applies. A carrier’s delivery message may differ from the customer’s confirmation of the agreed condition.
The design links commercial consent, required payment authorisation, the condition and the exact instruction. Time limits must be clear to both parties. A dispute arising meanwhile should follow an agreed procedure. The system should not invent an answer to who is right in a commercial disagreement.
Sending and refunding are separate actions
Before actual submission, check current consent, fulfilment and authority again. After provider acceptance, the actual operation state determines the next steps. Lost confirmation requires enquiry into the original outcome. Changing an internal status after completion does not itself return funds.
Our proposed refund is therefore another authorised operation linked to the original trade. Record its reason, the responsible person’s decision and the refund outcome. Applicable contracts and law determine customer rights and merchant duties; this working design does not decide them.
How to recognise a useful feature
Test ordinary acceptance alongside refusal of the condition, expired consent, an unknown outcome and a refund. Each state needs a clear explanation for customer and company. A green success screen alone leaves exception handling unmeasured.
The output should trace consent through payment and related records, with a person available to resolve problems. This makes conditional payment benefits assessable. Automation should improve a particular transaction whose rules both sides understand.
Implications for Czech and Slovak companies
For a Slovak company or a Czech company trading in euro, this is preparation of requirements rather than activation of a finished service. Availability depends on the final legal framework and provider. This article does not anticipate an issuance decision or participant selection after 1 November 2026.
Sources
- ECB — New digital euro innovation platform activities, 28 September 2026 — subject basis
- ECB — Digital euro innovation platform — subject basis
- ECB — Digital euro innovation platform outcome report, September 2025 — subject basis
- ECB — FAQs on the digital euro — further context
- ISO 20022 — About the standardisation approach — further context
- CPMI–IOSCO — Principles for Financial Market Infrastructures — further context
- CPMI–IOSCO — Guidance on cyber resilience for financial market infrastructures (2016) — further context
- EU — Regulation (EU) 2016/679: personal data protection — further context
- GLEIF — Engagement Context Role credential framework v1.5 (March 2026) — further context
- CPMI — The roles of central banks and central bank money in the evolving payment system (29 October 2026) — further context
Methodological note: The article distinguishes documented institutional information from editorial analysis. Numbered references identify direct evidence and professional or legal context. A contextual source does not document this particular transaction. Hypothetical examples are editorial illustrations, not findings about an actual client. A later planned publication date does not advance the verification cutoff.
Notice: For information and education. This is not investment, legal, tax or accounting advice, or an offer of a financial service. Any application requires individual assessment. The institutions mentioned are not partners or guarantors of Tokenizace.cz.
What this means for you
AI puts the article in the context of your role, company and industry. Choose the one working document you need now.
Saved outputs and notes are private. Making your profile public does not share them with other users.
Loading account…
Context and outlook
Loading…
Open the full category →Comments
No comments yet. Be the first!