Identify merchants from transaction text in reviewed documents
Use a recurring document review to turn raw transaction descriptions into merchant brand details.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Identify Merchant from Transaction
Why this helps
Raw transaction text is often hard to recognize, creating extra research during document review.
- Process unstructured transaction text through a merchant identification action.
- Gather brand details for review in one run.
- Use a recurring schedule for document batches.
Setup
Build it in a few focused steps.
- 1Connect Affinda and Brandfetch once in the Notis portal.
- 2Create an automation that describes which documents and results to review.
- 3In one instruction, ask Notis to find raw transaction descriptions in available documents and identify the merchants through Brandfetch.
- 4Set a recurring schedule and choose where run reports go.
- 5Test with one real document and confirm the merchant result.
Questions about this workflow
How is this different from looking up a transaction label?
Identify Merchant from Transaction is described for raw, unstructured payment text and returns brand details, including name, logo, domain, and industry information.
Does Affinda automatically trigger the recurring run?
No. The Notis cron schedule starts the automation, which then works with the documents specified in its instruction.
Can it identify every transaction description?
Results depend on the text and Brandfetch matching. Have Notis report unclear or unmatched descriptions for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Affinda to Brandfetch. A trigger fires from one place; an action lands in another.
Affinda triggers
Brandfetch actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Brand Information
Retrieves brand details such as logos, colors, fonts, and company information.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get GraphQL API Version
Retrieves the current GraphQL API version.
Get Brandfetch Taxonomy
Retrieves the classification taxonomy of industries, countries, and regions.
Get Transaction Info
Identifies a merchant from a transaction label and returns its brand information.
List Subscribable Events
Lists available webhook event types and their descriptions.
Search Brands
Searches for brands by name and returns matching brand information.
List Webhooks
Lists webhook configurations and their statuses.
Connect any two apps with Notis in the middle.
Affinda and Brandfetch, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Brandfetch.