Safe to include
Provider transaction and payout IDs
Merchant or order references
Operational timestamps and states
Currency and transaction amounts
Fees, net settlement, routes, and markets
Data and connections
Every source should arrive with its meaning intact.
Palyra is designed for API, webhook, SFTP, and controlled-file ingestion. Every source is validated, mapped into a canonical payment lifecycle, and kept attributable to its provider and workspace.
Controlled file ingestion
Start safely while recurring connections are verified.
Sanitized CSV imports are the available bridge for real workspace evidence. The templates show the common fields Palyra can recognize without including customer or cardholder data.
Canonical operational evidence
Identity
record type, provider record ID, merchant reference, customer reference
Timing
event timestamp, settlement timestamp
State
transaction status, settlement or payout status
Value
currency, gross amount, fee amount, net amount
Route
payment method or route, country or market, settlement batch ID
Remove before import
Card numbers or PAN
CVV, CVC, or security codes
Card expiry dates
Customer names, emails, phones, or addresses
Passwords, API keys, tokens, or credentials
Matching rules
Every comparison remains explainable.
Exact match
Merchant reference + currency + gross amount
Reference fallback
Reference + currency when amounts differ
Unmatched review
Remaining records become missing-counterpart checks
Quality checks
States, settlements, duplicates, and fee thresholds
Provider exports can describe different stages of a payment journey. Palyra keeps source windows, mappings, and provider-specific definitions visible so a team can verify material differences.
Start with the evidence you have, then move into recurring connections as coverage is verified.
Schedule a focused walkthrough or create a workspace for your own payment operation.