Integrations

The Acrontec Marketplace Engine connects to proven cloud services for payments, maps, push, messaging, storage, and security. Providers below are what the licensed reference stack (Nectar Eats) is built to use — many are toggleable per install in admin settings.

Supported integration categories

Payment gateways

Card, wallet, and commerce checkout wired through the payment layer.

Stripe
PayPal
Coinbase Commerce
In‑app wallet / cash flows (platform‑native)

Maps & location

Zones, geocoding, distance, and live maps on web and mobile.

Google Maps Platform
Places autocomplete & geocode APIs
Distance / routing helpers for delivery fees

Notifications & messaging

Push, SMS OTP paths, and transactional email.

Firebase Cloud Messaging (FCM)
Firebase Phone Auth (where enabled)
SMS gateways (Twilio, Nexmo/Vonage, Msg91, 2Factor — configurable)
Email via SMTP / Mailgun / Amazon SES / Postmark

Identity & security

Customer auth and bot protection for panels and forms.

Laravel Passport (API Bearer tokens)
Social login — Google, Facebook, Apple
Cloudflare Turnstile

Storage, cache & data

Media, queues, and high‑traffic caching.

S3‑compatible object storage
Redis (Predis)
MySQL (primary datastore)

Analytics & ops reporting

Operator insight plus optional storefront measurement.

Built‑in admin analytics & reports
Google Analytics (storefront, when configured)
Excel / PDF exports for ops documents

AI content tools

Optional operator tooling for menu and content assistance.

Laravel AI SDK
Configurable local / hosted LLM agents (e.g. Ollama)

Custom & enterprise

Licensed operators can extend the engine for their demographic.

Additional payment providers
Private partner APIs on /api/v3
Custom reporting or logistics connectors

API‑driven architecture

All first‑party clients (Next.js storefront, Flutter apps, vendor/admin tooling) share one versioned REST surface: /api/v3.

Payment gateways use provider‑specific callback/webhook URLs where required. There is no generic public “order event bus” for third parties — see Webhooks & realtime and the API overview.