FINANCE

Real-time out-of-policy card transaction blocker

Evaluates every Stripe Issuing authorization the moment it arrives against your merchant-category spend policy.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerStripe Issuing authorization request webhookStripeStripe
  • LogicMatch merchant category code against policy table
  • ActionApprove or decline the authorization in StripeStripeStripe
  • ActionLog decision, MCC, amount, cardholder to PostgresPostgreSQLPostgres
  • OutputAlert finance Slack channel on declinesSlack

What it does

Intercepts Stripe Issuing authorization requests in real time and decides whether to approve or decline based on your written spend policy. Banned merchant categories (gambling, cash advances, alcohol on travel cards) get declined at the point of sale; everything compliant is approved within Stripe's authorization window. Every decision is logged to Postgres for the audit trail.

When to use it

Run this when you issue corporate cards through Stripe Issuing and want hard enforcement rather than after-the-fact cleanup. It is the right tool when a category is simply not allowed and you would rather the card decline at the register than chase a reimbursement later.

How it works

  1. 1Stripe sends an `issuing_authorization.request` webhook the instant a cardholder swipes.
  2. 2A logic step reads the merchant category code and amount, then checks them against the policy table.
  3. 3If the category is on the banned list, the flow calls Stripe to decline the authorization with a reason.
  4. 4Otherwise it calls Stripe to approve the authorization.
  5. 5The decision, MCC, amount, and cardholder are written to Postgres for reporting.
  6. 6Declines post a short alert to the finance Slack channel so the team knows in the moment.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.