INTERNAL ONLY · FIRST PASS v0.1 Proposed positioning · Not approved policy
About this playbook
This internal playbook aligns how we explain Decentra, position Decentra Core and package our forward-deployed engineering offering in partner conversations. It brings together the key messages, a 15-minute narrative and practical guidance for discovery, objections and next steps. We will use it as the foundation for audience-specific customer presentations; it is a working draft, not material to share externally.
01 / Positioning · proposed
Make payment infrastructure ready for agentic commerce.
Decentra combines reusable financial-control IP with forward-deployed engineering to turn a defined agentic-commerce opportunity into a controlled, integrated payment workflow.
Decentra Core provides the control capabilities. FDE makes them useful in the partner’s environment.
This is our internal conversation playbook for networks, payment providers and ecosystem partners such as Visa. It is the source from which we will later carve a short, audience-specific presentation—not a document to forward as-is.
The discipline
State the message first. Explain second. Prove only what we can substantiate. Lead with the partner’s outcome; describe what Decentra Core does rather than how it works. Keep services, software rights, operational support and relationship claims distinct.
The 30-second opener
“Decentra implements its patented technology within payment providers to enable agentic commerce through the infrastructure they already have.
Decentra Core brings the buyer and seller together in a trusted, private transaction environment. It verifies identities, transaction details and payment authority, with all three parties agreeing to a shared, signed record before the payment intent is delivered to the provider for execution.
We also provide the tools, clients and integration primitives that let buyers, sellers and their agents participate across the provider’s network. Our forward-deployed engineers install Decentra Core and integrate and operationalize these capabilities within the provider’s existing systems.”
Positioning language describes our intended offer. It is not a claim that the full Decentra Core, every connector or a production partner integration is available today.
02 / Offer architecture
One proposition. Two assets. Explicit commercial boundaries.
We are neither an undifferentiated engineering shop nor a finished universal platform. We bring reusable IP and specialist delivery, selected against the actual gap.
Decentra Core / reusable IP
Its role is to connect agent intent to accountable financial action: verify authority, apply agreed transaction constraints, connect to permitted execution and preserve evidence of the outcome.
Partner value: a reusable foundation for supported workflows, rather than re-solving the same control problem in every integration.
Not implied: universal protocol coverage, complete corporate spending infrastructure, a new payment rail or mandatory adoption of the full stack.
FDE / specialist delivery
Embedded engineering defines the use case, reuses what exists, integrates the missing boundaries, tests failure paths and transfers the agreed operating capability.
Partner value: progress from an abstract agentic-commerce ambition to an accepted workflow in a named environment.
Not implied: unlimited development, guaranteed production launch, automatic Decentra Core licensing or ownership of all work produced.
Package the work by the decision it enables
Proposed package
Partner receives
Exit decision
Opportunity & readiness discovery
Journey definition, gap assessment, interface and authority map, acceptance plan and scoped estimate.
Build, configure an existing feature, defer or stop.
Bounded workflow proof
Agreed test integration, authority controls, outcome handling, positive/adverse test evidence and known limitations.
Accept the proof; decide whether to fund production preparation.
Authorized release for the named workflow and environment.
Decentra Core access & maintained capability
Explicit software rights, supported interfaces/versions, maintenance and support responsibilities.
Agree the ongoing entitlement, service boundary and economics.
Commercial rule of thumb: engineering fees buy defined delivery; licensing buys defined IP rights; support buys defined operational obligations. Usage pricing is an option to evaluate, not an entitlement to a fee on every transaction. Avoid charging twice for the same obligation.
Package names and sequence are a first-pass proposal, not approved SKUs or pricing. FDE acceptance stands independently of future licensing or distribution. Background IP, customer IP, foreground work and reuse rights require explicit agreement.
03 / Message-first call spine · 15 minutes
Earn the next decision, not a broad expression of interest.
Seven beats, each with a statement the listener can repeat. The timing is a rehearsal budget for the presentation; discovery and discussion need additional time or a shorter narrative.
Beat 01 / The offer1 min
Decentra makes existing payment infrastructure ready for agentic commerce.
Lead with the outcome and the two assets: reusable Decentra Core IP plus FDE delivery. Anchor on the counterpart’s ecosystem, not our architecture.
Talk track & meeting cue
“We bring the control capabilities and the engineering needed to connect agent-driven workflows to existing payment services. We want to understand which part of that problem matters in your ecosystem and where your existing capabilities already solve it.”
Visual to carve later: independent agents → scoped Decentra controls → existing payment infrastructure. Label as a conceptual role map, not mandatory routing or funds flow.
Transition: “The difficult boundary is not just connecting an agent. It is establishing what it may do.”
Beat 02 / The gap2 min
A payment request is not permission to pay.
An agent can research, recommend or request. The receiving business still needs a verifiable actor, payer authority, exact transaction scope and a reliable outcome.
Talk track & discovery cue
“Knowing which agent is calling does not tell you what the buyer authorized. Permission must apply to this payee, this amount and these conditions—and remain connected to what is actually submitted.”
Ask: “Where do you expect that authority to originate, and who owns enforcement today?”
Avoid: saying existing network, fraud or identity controls are absent or obsolete. Establish a specific gap before asserting one.
Beat 03 / Decentra Core’s role2 min
Decentra Core connects agent intent to controlled, accountable transactions.
Four jobs: establish financial authority; apply transaction constraints; connect permitted instructions to existing execution; preserve outcome evidence.
Talk track & boundaries
“Decentra Core’s role is to help determine whether an agent may take this financial action and keep that decision connected to the result. The agent still does its business reasoning; the provider still processes the payment; the enterprise still owns its records.”
What stays out: the six-layer architecture, sealed-execution mechanics and patent arguments. Use a technical follow-up when needed.
Evidence boundary: selected repository components support narrower control and integration patterns. Do not describe the complete role as an already validated end-to-end partner product.
Beat 04 / Delivery2 min
FDE turns reusable capability into a working partner offering.
Define the journey → connect the boundaries → validate behavior → establish operating ownership. Start by reusing existing partner capabilities.
Talk track & tangible outputs
“We work with your team on a defined journey and deliver the integrations, tests and operating handoff it requires. We separate what is specific to your environment from reusable Decentra capabilities and agree the rights explicitly.”
Bring: an illustrative deliverables list, acceptance criteria and interface map—not an unsupported delivery-date promise.
Boundary: a successful proof does not automatically mean production approval, platform adoption or downstream merchant activation.
Beat 05 / Concrete example3 min
One invoice makes the trust boundary tangible.
Use a proposed buyer-agent invoice-payment journey. It explains the roles without requiring two Decentra-operated agents or a new payment rail.
Seller exposes the invoice.Conventional AR software is sufficient; a seller agent is optional.
Buyer’s agent checks the obligation.Commercial truth stays with buyer/seller records and their processes.
Buyer grants exact permission.The invoice itself is not consent. Missing or refused approval stops the action.
Decentra verifies the permitted financial action.Check identity, current authority, transaction details and duplicate state within the selected design.
The existing provider executes.Provider payment authorization and settlement responsibilities remain unchanged.
Each organization reconciles verified outcomes.A timeout is unresolved, not an invitation to pay again.
Talk track & proof posture
“The buyer keeps spending control, the seller need not replace its software, and the provider keeps execution. Our job is to integrate the authority and outcome boundaries so the workflow can be tested and operated.”
Label: illustrative proposed workflow, not a live Payroc deployment. One synthetic invoice is an early technical milestone, not the full proposed Payroc program.
Ask: “Is this representative of a gap you see, or is another workflow more valuable?”
Beat 06 / Ecosystem value3 min
A provider connection can become a repeatable ecosystem offering.
Begin with one valuable journey; qualify what can be reused across supported products, ISVs and merchants. Treat lower delivery effort and distribution reach as hypotheses to measure.
Talk track & Visa angle
“The opportunity is not only a custom integration. If we establish a useful provider boundary, parts of the control and integration work may carry into additional workflows and participants. We want to understand where that would complement your existing programs and capabilities.”
Visa working hypothesis: ecosystem enablement made concrete through a provider-linked reference journey. Visa may help identify requirements, counterparts and a validation route; no program access or role is assumed.
Keep separate: provider delivery terms, Decentra Core licensing, network collaboration and participant adoption. There is no automatic network revenue share or mandatory middleware routing.
Beat 07 / The ask2 min
Select one opportunity and agree what would prove it.
Leave with a named problem, accountable counterparts, required evidence and the next decision. An owner or due date is only agreed when the counterpart confirms it.
Closing words & fallback
“Which provider-linked workflow would be most useful to evaluate together, who should own the technical and business work, and what evidence would enable a decision on the next stage?”
If interest is exploratory: seek a requirements/discovery session, not a premature pilot announcement.
If the gap is already covered: understand the existing route and decide whether integration help is still useful—or stop.
04 / Audience adaptation
Keep the proposition stable. Change the relevance and the ask.
Room
Lead with
Discover
Next decision
Network / Visa-like partner
Enable the provider ecosystem without replacing existing roles.
Applicable requirements, existing programs/capabilities, participant route and business owner.
Confirm technical/commercial counterparts and a candidate validation path.
Gateway / processor / acquirer
Turn a selected product into a controlled agent-accessible workflow.
Actual API/product boundary, payer authority, payment method, status/recovery and demand.
Fund and scope discovery or a bounded proof with acceptance owners.
ISV / merchant infrastructure
Connect an existing business workflow to permitted agent-initiated payments.
System of record, invoice/order access, existing connectors and designated accounting writer.
Select a participant journey and integration responsibilities.
Enterprise buyer / agent ecosystem
Keep buyer control while allowing independent agents to act.
Approval source, scope, revocation, operating owner and existing provider path.
Qualify one supported buyer-side interaction, not a forced agent migration.
Visa preparation
Do not lead with “buy our platform.” Test whether Visa sees a relevant ecosystem gap, then establish who owns requirements and evaluation. Direct procurement, distribution and reference collaboration are different paths; choose after discovery. Any Payroc example requires permission-appropriate wording.
05 / Qualification
Find the valuable gap before prescribing Decentra Core.
Business questions
Which agent-initiated journey is blocked today, and for whom?
What new offering, revenue opportunity or operating improvement would solving it enable?
Who owns the outcome, budget and acceptance decision?
Which participants actually want to use it? Provider access does not establish buyer adoption.
Delivery questions
What already exists across provider, network, ISV, ERP, identity and risk services?
Who grants payer authority, who submits the instruction and who resolves unknown outcomes?
Are approved test environments, a usable payment method and lawful data access available?
Who owns the accounting write-back, operations, support and maintenance?
What happy-path and adverse-path evidence would both sides accept?
Commercial and rights questions
Is this paid discovery, a funded proof or explicitly bounded exploratory work?
What software rights are needed, and which work is partner-specific?
What may Decentra reuse? Customer confidential material does not become reusable learning by default.
What existing fee includes each obligation? Which recurring obligations justify recurring charges?
Go / not yet / no-go: proceed when the problem, sponsor, boundary, access and evidence criteria are sufficiently defined. Otherwise propose bounded discovery. Decline generic AI work outside the payment-enablement mission or work with unresolved authority and access.
06 / Response patterns
Answer the concern. Do not defend unnecessary infrastructure.
“Why can’t we build this ourselves?”
You can. The decision is whether reusable controls and specialist delivery reduce effort or risk for this workflow. Compare our actual scope, evidence, integration cost and ongoing obligations against an internal build; do not claim inevitable cost savings.
“Our network or processor already does this.”
Start there. Identify exactly which authority, interface and recovery requirements are covered. Configure or integrate existing features where sufficient. Decentra should fill a meaningful gap, not duplicate controls.
“Are you another agent platform—or a payment processor?”
Neither is required by this offer. Independent agents retain business reasoning; existing providers retain payment execution. We supply scoped financial-control capabilities and delivery around those boundaries.
“What is proprietary versus custom engineering?”
Separate Decentra background IP, partner systems/data and engagement deliverables. Identify the exact components and rights in scope. Do not use the patent thesis as proof of delivered capability, granted protection or exclusive market access.
“Is it live? Can we see it?”
Name the exact component, version, environment and test result we can show. The source atlas reports bounded local patterns, not a production Payroc integration or fully validated end-to-end Decentra Core. Offer an evidence-led technical session rather than overstating a demo.
“Can you support every protocol and ERP?”
No blanket claim. Confirm the required products, versions, operations and authority semantics. Publish a supported matrix and identify the adapter work; named ERP discovery targets are not existing connectors.
“How do you get paid?”
Defined engineering work, optional software rights and separately scoped maintenance/support. Usage-linked economics may fit some engagements after value, costs and permissions are established. No generic rate or Visa/Payroc term is approved by this playbook.
07 / Claim discipline
Be confident about our role. Be exact about our evidence.
Topic
Working statement
Boundary / evidence required
Decentra Core
Intended financial authority, transaction-control and evidence role.
Component-specific implementation and tests before claiming delivered end-to-end scope.
Existing software
The internal atlas reports bounded catalog, checkout, wallet and merchant patterns.
Second-hand repository assessment here; not a fresh code audit or live-provider acceptance.
FDE
Proposed specialized integration, validation and handoff offering.
The operating standard is an unapproved historical candidate, not effective company policy.
Payroc
Candidate provider-linked gateway, ISV/merchant and AR workstreams.
Attributed direction/proposal, not a signed scope, live integration or participant commitment.
Visa
Target for requirements, ecosystem and collaboration discussion.
No endorsement, investment, program acceptance, resources or approved announcement assumed.
IP
Separate reusable Decentra IP from partner-specific delivery.
Rights and patent status need documentary/legal verification. No monopoly or granted-claim assertion.
Economics
Services, license, support and potential usage models can be evaluated.
Pricing Foldy is an assumptions-based scenario lab, not an offer, booked revenue or forecast commitment.
Aegis
Separate, optional reference technology.
Not Decentra product IP, a mandatory dependency or evidence of a partnership.
Evidence ladder: concept → local/synthetic test → provider sandbox → participant acceptance → production approval/operation. Never skip a stage in the language because a demo looks complete.
Readiness is scoped: supported workflow + environment + version + owner + dated evidence. “Agent-ready” is not a universal company-wide badge.
08 / Meeting preparation & follow-through
Capture an accountable next step.
Use this checklist to prepare and close. Inputs are saved only in this browser’s local storage, not to the Foldy project or other users. Do not enter credentials, sensitive customer data or unapproved relationship details. Export a local JSON record if needed.
Local notes only. Nothing is submitted.
09 / Management review before external carve-out
Resolve the offer before polishing the slides.
Approve the opening message. Is “payment infrastructure ready for agentic commerce” our primary category language?
Confirm Decentra Core packaging. Which exact components and capabilities can we offer now, and which remain roadmap?
Choose the first audience and ask. For Visa, validate ecosystem enablement/reference collaboration versus direct procurement.
Approve FDE boundaries. Package names, deliverables, staffing, acceptance and support need actual operational owners.
Clear proof points and IP language. Confirm reusable rights, component maturity, customer permissions and patent wording.
Restore authorized access to the latest Decentra Core architecture. Incorporate Transaction Dossier terminology only after reviewing the actual artifact.
Carve a separate customer artifact. Remove internal notes, relationship registers, scenario pricing and source limitations inappropriate for that audience; retain accurate capability and maturity labels.
Review checkboxes are not approvals. No policy, pricing, contract, production authority or customer commitment is created by this draft.
10 / Provenance & coverage
A synthesis of the working material—not a new source of truth.
Prepared from the Decentra Foldy project inventory and retrieved entry pages. Nine related projects were identified; eight entry pages were retrieved. The Aegis entry is a thin workbook-derived shell; its full workbook and companion files were not audited. This is not an exhaustive repository, attachment or companion-file review.
Provider-facing language, existing-rails framing and build/buy/reuse alternatives. Artifact title does not establish current public access or clearance.
Inventory metadata only. Entry and raw access returned HTTP Basic 401 during preparation. Full contents not reviewed; no claim of complete context.
Hosting & information boundary
New internal-workspace intent; no public deployment is requested. “Unpublished” metadata is not proof of authentication or confidentiality. Restrict sharing to authorized internal readers and confirm access controls before adding sensitive material. This draft contains internal strategic synthesis.