Sandbox access is used to coordinate a validation of your Omni integration with Percents. It is not a live transaction-processing environment.
Use sandbox to verify that your issuer can:
- authenticate with its server-side API token;
- read its merchant and offer catalog;
- request and upload an agreed test transaction file; and
- receive, verify, and process the processing-result webhook.
The sandbox is designed for contract and integration validation. It does not process live cardholder transactions, create production rewards, or provide a fixed-schedule simulation of production processing.
Native and Plaid files are validated as complete files. The signed FileUploadProcessingResult webhook and persisted file status report processingStatus=validation_only with validationStatus=passed when validation succeeds. Failed validation reports processingStatus=failed with validationStatus=failed. No live transaction ingestion or production rewards occur in sandbox.
Storage acceptance does not mean validation passed. Retain the file ID and reconcile through the status endpoint or webhook. Contact support if the result is unexpectedly delayed.
Provide Percents with the issuer name, a public HTTPS webhook URL, and the file format you intend to validate. For network access, choose either stable public egress IPs or CIDR ranges for the source-IP-allowlist URL, or a CSR for the mTLS URL. Percents returns sandbox API and webhook-signing credentials through an approved secure channel.
Use separate sandbox and production credentials. Do not upload live cardholder data to sandbox.