# Build an implementation of the standard

Choose one role, compose the existing primitives, and prove the operation through source, execution and recovery.

Canonical: https://docs.bankeiz.com/integrations/
Reviewed: 2026-10-25; coordinated packages 129.0.0; ruleset 127.0.0.

## Choose the role and operation

A receiver, issuer, custodian, verifier, merchant and application operator have different responsibilities. Begin with one supported operation and define its original source, exact units, participant identity, intended transition and completion evidence. Do not start with an invented ledger or a generic success boolean.

**A complete integration names each boundary**

| Boundary | Implementation question |
| --- | --- |
| Source | Which existing Original/verifier supplies the truth? |
| Authority | Which identity, owner, grant and exact-operation consent apply? |
| Execution | Which native operation and qualified storage commit the change? |
| Recovery | Which retained original reference resolves interruption? |
| Disclosure | Which proof can be shared and under what consent? |
| Assessment | Which build, realm, roots, rail and environment are actually tested? |

## Use the coordinated primitives

1. **Pin the coordinated packages** — Use the documented SDK, MCP and AI Skills release together.
2. **Read the exact entry points** — Use browser-safe/Node-only exports in their intended environments.
3. **Compose a supported operation** — Start with receiving or independent inspection before adding consequential execution.
4. **Keep complete source** — Retain original bytes, unknown namespaces and necessary predecessor closure.

## Digital Reserve and Settlement transfers

The value.edge reference verifies both participant sources and current heads, plans the intended rail, inspects wrapper.plan for each participant, obtains exact-operation consent, verifies the sealed transition set and prepares an all-or-none commit. A qualified store returns actual SDK-issued committed custody. createRecovery binds the accepted transition set and committed transitions before optional global synchronization. A SQL success, property bag or serialized handle cannot mint that custody.

- [Inspect the typed edge-payment reference](https://github.com/kojibai/reality-grade-banking/blob/6c5d582/institution/examples/edge-payments.ts)

## Exercise interruptions and refusals

Test wrong recipient, changed amount/rail, unsupported source, missing parent, stale head, duplicate request, concurrent commit, lost response and restart. Recover the same intent at each irreversible boundary. Retain accepted and refused source evidence. Never hide a possibly committed operation by replacing its intent or restoring an already consumed predecessor.

## Qualify the actual capability

Local sandbox, typecheck, contract testbench, independent original verification and deployed financial/hardware assessment are different evidence. Name the exact supported scope and missing boundary. No Bankeiz purchase, permission or badge is required for independent implementation/assessment. Publish only authorized safe evidence references; keep private originals under protected custody.

- [Complete conformance procedure](https://docs.bankeiz.com/conformance/)
- [Runnable SDK sandbox](https://docs.bankeiz.com/sdk/)

## Implementation sources

- [Normative receiving requirements](https://github.com/kojibai/reality-grade-banking/blob/6c5d582/institution/receiving-standard.md)
- [Value-edge lifecycle](https://github.com/kojibai/reality-grade-banking/blob/6c5d582/institution/digital-payments.md)
- [Receiver evidence and release checks](https://github.com/kojibai/reality-grade-banking/blob/6c5d582/institution/qualification.md)
- [Independent integration/assessment path](https://github.com/kojibai/reality-grade-banking/blob/6c5d582/docs/conformance/integration-and-assessment.md)

## Related documentation

- [Start with the Receiz SDK](https://docs.bankeiz.com/sdk/)
- [Accept payments and fulfill an order once](https://docs.bankeiz.com/merchant-checkout/)
- [Assess an implementation independently](https://docs.bankeiz.com/conformance/)
- [Versions, schemas and implementation status](https://docs.bankeiz.com/compatibility/)