Connect a merchant account

Confirm that a merchant's provider account is ready before it appears in checkout.

After a merchant installs your app and finishes setup, Tringify asks your connection capability endpoint to describe what that account can use right now. This keeps checkout accurate when provider plans, regions, credentials, or account approvals differ.

Receive the connection check#

Verify the Tringify signature before reading the request. Use the binding ID to load the matching merchant configuration in your app.

connection-check-request.json json

{
  "binding_id": "bnd_…",
  "store_id": "store_…",
  "app_id": "app_…",
  "service_type": "payment",
  "connection_key": "default",
  "declaration_revision_id": "revision_…"
}

Report the account's current capabilities#

Return ready only when the account can accept requests. Return requires_action when the merchant still needs to finish setup, or error when the connection cannot be used. Every operation and currency must already exist in the approved declaration.

connection-check-response.json json

{
  "status": "ready",
  "mode": "test",
  "health": "healthy",
  "account_country": "IN",
  "account_hint": "Connected test account",
  "operations": [
    "charge",
    "refund"
  ],
  "presentment_currencies": [
    "INR"
  ]
}

Test and live accounts#

Report mode: test for sandbox credentials and mode: live for production credentials. Never infer the mode from a label entered by the merchant; determine it from the credentials or provider account you have verified.