Acceptance Criteria

A Kaya Sync journey is not considered complete unless all of the following are true. This is the bar for the full Originator-to-Designee flow.

1. The originator or facilitator created a transaction with a valid designee phone number.
2. The designee phone number was physically visible on the cargo before dispatch.
3. Origin evidence was captured and validated.
4. The first-mile operator was authenticated and device-bound.
5. The first-mile pickup created a valid custody event.
6. Each custody transfer had dual evidence unless a controlled exception policy applied.
7. Any aggregation or disaggregation was event-recorded.
8. Any relabel or repack was authorised, evidenced and auditable.
9. The last-mile operator captured final delivery evidence.
10. The designee confirmed receipt through a low-friction method.
11. The system produced PASS or PASS WITH TOLERANCE before payout release.
12. Any HOLD / FAIL created a reviewer-visible evidence bundle.
13. Settlement records matched delivery validation records.
14. Enterprise / regulator exports, where applicable, used controlled data access.
15. The full transaction could be reconstructed from the event ledger.

How to use these criteria

• QA: write acceptance tests that exercise each of the 15 items end-to-end.
• Engineering: every new feature must preserve all 15 criteria.
• Operations: incident review should check which criterion failed first.

Source

Kaya Sync — User Journeys: Originator to Designee, §10.