Card-Linked Transaction Feeds

Fidel API links a payment card to a program, so a transaction on that card generates a data feed the moment it clears, rather than requiring a receipt or statement upload. A Beam agent reads each transaction event as it arrives, matches it to the customer or account it belongs to under a team's approved rule, and files it against the relevant loyalty, cashback, or expense record. This removes the delay of waiting for someone to submit proof of purchase. Transactions from an unenrolled card, or ones that don't match any known account, are set aside for a person to look into.

Merchant Category Matching

Each transaction Fidel API returns carries merchant details, including a category such as travel, dining, or retail, which a program can use to decide what happens next. A Beam agent reads that category against the approved rule for a given program, such as awarding a reward only for purchases at a qualifying merchant type, and applies or withholds the reward accordingly, updating the customer's record either way. This keeps reward logic tied to real purchase data instead of a self-reported claim. Transactions with an unclear or missing merchant category are held rather than resolved automatically, and passed to a person to classify.

Card Enrollment and Consent Tracking

Before any transaction data can flow, a cardholder has to enroll their card and grant consent, a step Fidel API tracks alongside the resulting data feed. A Beam agent checks that a card's consent record is current before acting on any transaction tied to it, and where consent has lapsed or been withdrawn, the agent stops filing new transactions against that record and notifies the program owner. This keeps a program working only with cards a person has actually approved for tracking. Renewals, disputes over consent, and any card flagged for review are handled by a person rather than the agent.