POS Integration Support
Supported systems, SLAs, and troubleshooting
Integration Setup:
- • Admin approval: Within 24 business hours of request submission
- • Credentials generation: Automated immediately upon approval
- • POS configuration: Establishment responsibility (guided documentation provided)
- • Full integration active: 2-5 business days from approval
Issue Resolution Times:
- • Critical (transactions failing): 4-hour response, 24-hour resolution target
- • High (degraded performance): 8-hour response, 48-hour resolution target
- • Medium (non-critical bugs): 24-hour response, 5-day resolution target
Important: RKEEPER cannot guarantee resolution of issues caused by POS vendor outages, API changes, or establishment-side configuration errors. We will coordinate with vendors as needed.
SquareSupported
API v2024-01-18
Features:
Setup Time:
2-3 business days
Notes:
Most popular, easiest integration
ToastSupported
API v2.0
Features:
Setup Time:
3-5 business days
Notes:
Restaurant-specific features
CloverSupported
REST API v3
Features:
Setup Time:
3-5 business days
Notes:
Requires Clover developer account
Shopify POSPlanned
TBD
Planned for Q2 2026
LightspeedPlanned
TBD
Planned for Q3 2026
❌ "Transactions not processing"
Diagnostic Steps:
- 1. Check if POS system is online and operational
- 2. Verify RKEEPER platform status (check recent transactions from other establishments)
- 3. Confirm API credentials are still valid (not revoked/expired)
- 4. Check webhook configuration in POS admin panel
- 5. Review error logs in RKEEPER dashboard
Resolution: If RKEEPER is operational but POS integration fails, contact therealrkeeper@icloud.com with error details.
⚠️ "Webhook signature validation failed"
Cause:
The webhook secret in your POS system doesn't match RKEEPER's stored secret.
Resolution:
- 1. Log into RKEEPER dashboard → API Apps
- 2. Find your POS integration and copy the webhook secret
- 3. Update webhook secret in your POS admin panel
- 4. Test by processing a transaction
🐌 "Slow transaction processing"
Possible Causes:
- • POS vendor API slowdowns (check vendor status page)
- • Network connectivity issues at establishment
- • High transaction volume (peak hours)
Resolution:
If slowdowns persist beyond 1 hour, contact support. Most slowdowns are temporary and resolve automatically.
🔄 "POS vendor API change broke integration"
Known Issue: POS vendors occasionally update their APIs, which may break existing integrations.
When this happens, RKEEPER will:
- 1. Notify all affected establishments within 2 hours of detection
- 2. Begin updating integration code immediately
- 3. Deploy fix within 48 business hours (priority P2)
- 4. Coordinate with POS vendor if needed
Your responsibility: Keep your POS system updated to the latest stable version and notify us immediately if transactions stop working after a POS update.
When to escalate to RKEEPER:
- • Transactions failing for more than 1 hour
- • Webhook validation errors that persist after reconfiguration
- • Data sync issues (inventory, transactions not updating)
- • API credential errors after verification
When to escalate to POS vendor:
- • POS system offline or unresponsive
- • POS app crashes or errors
- • Hardware issues (card reader, printer, etc.)
- • POS account/subscription issues
Contact RKEEPER Support:
Email: therealrkeeper@icloud.com
Include: Establishment name, POS system, error message, and when issue started