Skip to content
Hypamoon

For teams that run on Moss

Moss subscriptions overview per card and person

When a user is deactivated in Moss, their cards are terminated, and Moss advises moving subscription cards to someone else first. Moss offers merchant cards and a tool that finds recurring payments in uploaded statements. Keeping track afterwards of which subscription runs on whose card is a manual job, and a reviewer writes that it is hard to see who holds which card.

How it goes today

  1. Download the card transactions of the last months from Moss.
  2. Sort them by merchant to find the payments that come back.
  3. Look up whose card each subscription is on.
  4. Ask the person before they leave which cards should move to someone else.

How it can go

Each recurring payment per merchant, card and person, with duplicates and leavers flagged.

At the start of each month you get a list of payments that come back every month, quarter or year: merchant, amount, last and expected next charge, card and the person Moss links the payment to. Merchants paid on more than one card are flagged, and so are payments on the cards of people who are deactivated in Moss or on the leavers list you keep. Moving or ending a card stays in Moss.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Moss key in the portal, never in the chat.

Your request

With Hypamoon, at the start of each month, find the card payments in Moss that come back each month, quarter or year. List them per merchant with amount, last and expected next charge, card and person. Flag merchants we pay on more than one card, and payments on cards of people who are deactivated in Moss or on the leavers list I keep. Email me the list.

As a Moss admin you create the API key yourself under Settings, Company Settings, API Keys, and confirm it in the Moss mobile app. Read access is enough for these tools. It stays yours.