A Consumer API integration must be certified before production credentials are made available.
Process
To initiate the certification process, a build (app or web) should be submitted
to the Thanx Developer Support team
(developer.support@thanx.com).
Once a build is submitted for certification, feedback will be delivered within
ten business days. If no critical feedback is provided, the build will be
certified and production API credentials will be issued. If critical feedback
is provided, integration partners should address the feedback and resubmit a new
certification candidate build, after which the 10 business day certification
review cycle will begin again.
Submission
Depending on the experience being developed, the following submission formats
are supported:
Web
URL of web experience
iOS
Firebase App Distribution link
TestFlight build. For the specific emails to whitelist, please request them
from developer.support@thanx.com.
Android
Firebase App Distribution link
APK file
All the above experiences must be pointing the Thanx Sandbox APIs. A build
should be submitted for each experience (web, iOS, Android).
Legal Requirements
User must agree to the Thanx Privacy Policy and Terms of Service when
creating a loyalty account. The language should read
User must be able to navigate to the Thanx Privacy Policy and Terms of
service from both App and Web experiences when logged in (may also be
mentioned in another document that’s readily available in the app, e.g. the
brand’s Terms)
Any screen where the user is enrolling their credit card for loyalty tracking
must have the correct legal text (see
enrollment best practices)
automatic - cash-back pushed directly to a user’s credit card once a
qualifying purchase is made
Supported coupon code formats:
Only in-use coupon code types need to be supported
raw
qrcode
barcode39
barcode39extended
barcode93
barcode128
barcode_upc_a
barcode_ean_8
barcode_ean_13
barcode25interleaved
Reward activation request should be made only on user action
Manual redemption rewards should display a countdown timer
When testing fraud-protected reward types (intro, invite, birthday, winback,
newsletter), use a unique, real card per test account. Shared test cards
(e.g. Visa 4111…) match on card fingerprint across accounts and merchants,
which flags the reward as fraudulent and makes it disappear on activation.
General API testing with shared test cards is fine — only fraud-protected
reward activation hits this.
Expression of Loyalty
The following expressions of loyalty are optional and the usage of these can be
determined by an integration partner’s creative/marketing teams.
That said, a requirement of the card networks is that a user must be able to
receive value in exchange for enrolling their card and authorizing Thanx for
automated data capture. Support for points, tiers, or both is required to
satisfy this requirement.
Experience should request all required information from the user
Experience should allow the user to choose a card to associate the receipt
with, if they have any
Product Guide
As part of certification, you must submit a product guide covering all use cases submitted for certification. The product guide must include:
Screenshots of each step in the flow
A screen recording demonstrating how the integration works
Share the product guide with the Thanx team via email. This is required before production credentials are issued.
Launch Notes Subscription
Subscribe to Thanx Launch Notes. All partners integrating with Thanx must subscribe to Thanx Launch Notes to receive new API, roadmap, and product-change announcements relevant to their integration. New integrations confirm their subscription during certification.
Postman API Collection
Here you will find the Custom App - Web Experience API Postman Collection to import directly within your API testing tool.
This collection is already completed and includes sample values for the credentials.Please replace them with the ones provided by your Thanx representative in order to achieve successful API calls.You can find more information about credentials and headers on the following page, or check the documentation for the specific API endpoint you want to call to ensure that all credentials are placed correctly.Download Postman Collection
Assistant
Responses are generated using AI and may contain mistakes.