A provider app connects a service the merchant already uses, such as a payment gateway, an SMS or WhatsApp account, or a shipping company, to Tringify. Your app keeps the merchant's credentials for that service and talks to it; Tringify never sees them.
Service |
How Tringify uses your app |
Guide |
|---|---|---|
Payments |
Calls your app to charge and refund, and shows the payment methods in checkout for the markets the merchant assigns. |
|
SMS and WhatsApp |
Calls your app to send each message, such as sign-in codes and order updates. |
|
Fulfillment |
Assigns orders at the locations the merchant chooses; your app ships them and reports tracking through the Store API. |
Declare the service#
Add a provider declaration to the app's draft, in the Developer Portal or under providers in tringify.app.json. It names the service, the operations you implement and, for payments and messaging, the HTTPS endpoint for each operation. Payments and fulfillment come with required Store API permissions, which the Developer Portal adds to the app's scopes for you. A provider can be part of a Standard app or a Sales Channel app, and one app can declare several services. The declaration is frozen into each release like the rest of the configuration: existing installations remain pinned to their installed revision until the merchant accepts an update.
What merchants do#
The merchant installs your app, connects their account in your app's pages, then chooses your app in Store Admin under Apps → Service Providers: as the store's SMS or WhatsApp provider, for payment methods per market, or for fulfillment per location.
Your responsibilities#
Store the merchant's credentials on your server, encrypted, and never return them in a response.
Verify every request from Tringify before acting on it.
Make retries safe: the same request can arrive more than once.
Report only what the service confirmed. An accepted message is not a delivered one; an authorized payment is not a captured one.