Build and troubleshoot
Use task guides, the rendered API reference, SDK examples, error meanings, and operations runbooks.
Open integration guidesBring the evidence. Reach the right path.
Use public guidance first, then contact Loyumi with a safe diagnostic summary for evaluation, integration, commercial, or production questions.
Public self-serviceHuman contact pathNo public response-time promise
Start with the artifact closest to the problem.
Security and procurement
Review implemented controls, internal tests, open assurance gaps, portability, and the production gates.
Open Trust CenterContact Loyumi
Send an integration, support, security-review, gifting, exchange, or loyalty-program question through the public contact form.
Contact supportUse one contact path with the right context.
evaluationName the proof step, expected outcome, actual outcome, and the public guide you followed.
integrationInclude environment type, API or client version, operation, status code, request ID, and whether a stable idempotency key was reused.
commercialDescribe the program, target date, scale assumptions, integration work, support needs, and procurement gates.
security reviewDescribe the evidence or control you need. Do not submit exploit detail or secrets through a general inquiry.
Share identifiers that explain—not authority that grants access.
Reviewable context
- Sandbox or Production—not a secret environment credential
- UTC timestamp and request ID
- Operation name, public status code, and sanitized error code
- SDK, CLI, API, or portability version
- Reproduction steps using synthetic identifiers where possible
Secrets and customer data
- API keys, signing secrets, bearer tokens, private keys, or claim capabilities
- Raw contact destinations or provider receipts
- Customer names, email addresses, phone numbers, or full exported records
- Production request bodies unless a secure channel is explicitly agreed
- Browser-session codes, gift claim links, or screenshots containing them
Contain first; use the contracted channel when one exists.
For an active Production engagement, follow the named support and escalation channel in the executed agreement. For evaluation or procurement, use the contact form. No public acknowledgement time, resolution target, dedicated security-reporting mailbox, or contractual SLA is promised here.