Native / custom store integration
For brands not on Shopify, Gatta can still run loyalty checkout — but the store must expose a small, stable commerce surface Gatta can call (or Gatta builds an adapter with you).
This page describes the integration contract at a product level. Exact OpenAPI bindings are provided during partner onboarding.
When to use this path
- Custom ecommerce / Magento / BigCommerce / headless
- Marketplace sellers with a private OMS
- Shopify Plus edge cases that need a bespoke order writer
Shopify brands should use Shopify integration first.
Responsibilities
| Party | Owns |
|---|---|
| Brand | Catalog truth, inventory, tax/shipping policy, fulfillment, customer notifications |
| Gatta | Loyalty quote, shopper payment (points + cash), settlement after you accept the order |
| Joint | Idempotent order ids, status webhooks, payout address, test checklist |
Required capabilities
1. Catalog read (discovery + quote)
Gatta must be able to:
- Search or list sellable SKUs by query (or accept a stable
variant_idthe agent already has) - Return: title, variant id, price, currency, availability
Pilot recommendation: start with known-SKU / brand-named purchases so catalog search quality is less critical than correct price + id.
2. Create pending order
After the shopper funds on Gatta, Gatta calls your API to create an order that is:
- Clearly marked awaiting merchant payment acceptance (or equivalent)
- Linked to a Gatta
intent_id(idempotency key) - Containing line items, email (if provided), and a short external reference
3. Accept payment webhook / callback
When your staff (or system) accepts payment — analogous to Shopify Mark as paid — notify Gatta:
POST {gatta_webhook_or_settle_endpoint}
Payload must include your order id and the Gatta intent_id (or agreed correlation fields). Gatta then finalizes loyalty settlement.
4. Payout destination
Provide an EVM payout address for USDC proceeds on the supported network (currently Base Sepolia for pilots).
Suggested auth model
- Mutual TLS or signed requests between Gatta and your commerce API
- Or: brand issues a scoped API key that Gatta stores encrypted
- Rotate keys without changing
brand_token_id
Do not put long-lived secrets in agent prompts or public repos.
Mapping to Gatta brand
- Complete Brand onboarding
- Gatta registers your adapter under your
brand_token_id - Fund loyalty reserve
- Run a joint test order end-to-end
Out of scope for v1 native adapters
- Full multi-warehouse ATP
- Complex promotions engines (beyond a single quoted price)
- Replacing your checkout UI for non-Gatta traffic
Related
- Brand overview
- Shopify integration (reference behavior to mirror)
- Operations