Your payment declaration is the promise your app makes to merchants. It lists the currencies and operations you are prepared to support. A connected account may offer fewer capabilities, but it can never add a currency or operation that was not reviewed in the declaration.
Payment protocol#
New declarations use payment protocol 1 automatically. The protocol defines the signed requests your app receives and the responses it returns. You do not need to choose a version when creating a new payment integration.
Support test accounts#
Turn this on when your app can connect sandbox credentials. During the connection check, your app reports whether the merchant account is test or live. Tringify accepts a test account only when this support was included in the approved declaration.
Currencies#
Presentment currencies describe the currencies your integration can process. The connected account reports its own account country during the connection check; country is not duplicated as declaration coverage.
Payment choices stay with your provider#
Do not copy card, bank-transfer, wallet, or device-specific payment choices into your Tringify declaration. Show the choices available to this customer inside your provider-owned payment experience. This keeps checkout accurate when provider availability changes by account, currency, customer, or device.
Operations#
Select only operations your app has implemented and tested. An operation with a dependency can be selected only when the required operation is also present.
Operation |
Value |
Purpose |
Requires |
|---|---|---|---|
Charge |
|
Create a shopper payment and collect it immediately. Your response chooses a redirect, provider modal, or embedded experience. |
None |
Refund |
|
Return the full remaining refundable amount of a successfully captured charge. |
None |
Partial refund |
|
Return a specified portion of a captured charge. Further partial refunds may continue until its refundable balance is exhausted. |
refund |
Status query |
|
Return the provider's authoritative result when an earlier operation timed out or its outcome is unknown, avoiding an unsafe duplicate retry. |
None |
Set up mandate |
|
Collect shopper consent and return a provider-owned mandate reference for future payments when the shopper is not present. |
None |
Off-session charge |
|
Charge a previously approved mandate without the shopper present, and report when it is expired, revoked, or needs fresh authentication. |
setup_mandate |