Contacting support (technical integration)

Support Inquiry Community

Who this article is for
For developers who find it hard to isolate the cause on their own, have doubts about ReceiptRoller-side behavior, or need urgent help.

The three support channels

Channel	Purpose	Response time
Developer community	Sharing knowledge with other developers, light questions	Varies
Support email	Bug reports, implementation questions, operational issues	2-3 business days
Emergency support	High-impact production incidents (outage or worse)	Within 1 business day

Checklist before contacting support

☐ Checked the status page
☐ Checked the relevant Developer Help article
☐ Searched the community for similar questions
☐ Checked your own recent changes (deploys, config changes)
☐ Gathered the required information (below)

Information to include (template)

[Summary]
(Describe the symptom concisely in 1-2 lines. E.g.: receipt.read intermittently returns 403 on the production app)

[Environment]
- App ID (client ID): rrapp_xxxxxxxx
- App name: MyApp Production
- Environment: production / staging / development
- API version: v1

[Time range]
- 2026-04-27 10:15 - 10:45 JST
- Ongoing / intermittent

[Scope of impact]
- All requests / only some
- Specific endpoint: GET /v1/receipts
- Specific store / all stores

[Steps to reproduce]
1. ...
2. ...

[Expected behavior]
200 with the receipt list returned

[Actual behavior]
403 returned, error.code: insufficient_scope

[Related request IDs]
req_01HV6N3M2K9PQR
req_01HV6N3M2K8XYZ

[What you checked on your side]
- Token verified as valid via /v1/me
- Scope includes store.read
- No recent deploys

What NOT to include

Caution: do not include the following in a support email.

Client secret (the client ID is fine)
Access tokens / refresh tokens
Webhook secret
Consumers' personal information (email, phone number, etc.)
Raw receipt body data

If these are needed, support will provide a dedicated, secure way to share them.

Contacts

Developer community: /en/developers/community
Support email: support@receiptroller.com
Emergency support: the dedicated channel provided at contract time (Slack channel, etc.)
Status page: status.receiptroller.io

Tips for getting a faster reply

Put the app name and symptom in the subject (e.g. "[MyApp Production] 403 recurring on receipt.read")
One inquiry = one issue (put multiple issues in separate threads)
Reply promptly to follow-up questions
When it's resolved, reply with a quick "resolved" (it also helps other users)

Related guides

Published: 2026-04-27 Updated: 2026-07-05

Back to help list