Send approved purchases and other verified evidence to Open Loyalty, or connect your own application through Steve’s API and webhooks. Keep your tools. Put verified data to work.
Start with a native integration built for your workflow.
Turn approved receipts into transactions and verified actions into custom events. Power your existing campaigns, points, and rewards with evidence checked by Steve.
Explore Open LoyaltySend receipt line items to the earning rules you already run.
Map evidence fields to custom events for your campaigns.
For Open Loyalty, the connection is built in. Bring your credentials, choose what to send, and test the flow.
Add your Open Loyalty instance and API credentials to your Steve organisation.
Select transactions for purchases or custom events for other verified actions.
Choose the data to send. Attach the customer email to submissions for member matching.
Approve a real test submission, check its delivery, and confirm the result in Open Loyalty.
Build Steve into your own customer experience with the API and webhooks. Submit evidence from your application and use the results in the systems you already run.
Built for developers, with API-key authentication, a webhook test endpoint, and polling when you need it.
Create a workflow session, upload your files, and submit them for processing.
Steve extracts the fields and applies your workflow’s verification rules.
Get completion and submission updates through signed webhooks, or retrieve results through the API.
What you need, what gets sent, and where to start.
Yes. Open Loyalty is a native connection, not a requirement. Your application can submit evidence through the API, receive completion and submission updates through webhooks, and retrieve results or review submissions through the API.
Your Open Loyalty instance and API credentials, a Steve workflow, and the customer email attached to each submission for member matching. Choose whether the workflow sends transactions or custom events, map the fields, and test with real evidence before launch.
For Open Loyalty, approved receipts can become transactions with line items. Other approved evidence can become custom events with mapped fields. For a custom integration, the API and webhooks provide processing results and submission status so your application can decide what happens next.
Steve records delivery outcomes so your team can see what was delivered and what needs attention. Retryable failures are retried automatically, and failed deliveries can also be retried manually. Fix invalid credentials or configuration before retrying those failures.
The native Open Loyalty connection handles delivery once you configure your credentials and field mapping. Connecting your own application requires a developer to implement the API flow and a webhook receiver, or poll for results. The quickstart walks through the steps; the full rollout depends on your workflow and customer experience.
Tell us which system you use, what evidence you collect, and where the results should go. We can help you assess the API integration and the setup your workflow needs.
Bring the system you use and the evidence you collect. We’ll help you work out how Steve fits into your workflow.
Discuss your integration 30 minutes. Your use case. Real possibilities.