Skip to content
PEYELIDocumentationPARTNER FIELD GUIDE / 1.3

Search the field guide

Local search · no data sentEsc to close
Partner guide/Integration
Data boundaries2 min read

Share the minimum that explains the outcome.

Public examples, private records and provider evidence have different disclosure rules.

Public evaluation uses synthetic data.

Public documentation and demonstrations should contain synthetic identities and records. A guided evaluation uses a dedicated tenant and selected fixtures. Customer records, KYC documents, private receipts, address books, credentials and raw payment payloads are not evaluation material for unrestricted sharing.

  • Agree on collection purpose, allowed fields and retention.
  • Use redacted evidence for partner reviews.
  • Keep each tenant’s records inside its authorized scope.

Assistance does not create financial authority.

The merchant assistant reads approved scoped tools; financial calculations come from services. Receipt extraction is requested by the merchant and produces a draft with uncertainty for review. A draft cannot confirm payment, post funds or replace the original evidence.

Where configured, extraction sends the selected document to the model provider. The implementation requests non-stored model responses, but provider handling, regional processing, retention and contractual terms still need explicit review for the intended deployment. Do not assume all data stays inside Peyeli.