framerstacks$ retweeted
Five things that haunt payment teams. Which one is keeping yours up at night?
framerstacks$ retweeted
A certification badge isn’t a force field. 🐸
Recent scrutiny surrounding LegitScript-certified merchants raises an important question: How do prohibited products make their way into the picture when a business has already demonstrated compliance?
Let’s be clear: LegitScript certification is a valuable credential, particularly in high-compliance industries like telehealth. It establishes an important layer of independent verification and helps processors assess merchant eligibility.
But certification and ongoing risk monitoring serve different purposes. One doesn’t invalidate the other.
Products change. Websites evolve. Business models shift. And sometimes, the frogs find their way into places they shouldn’t be. 🐸🔎
For payment processors, the responsibility doesn’t end with verifying credentials. We also need to understand whether the activity being processed continues to align with the business that was reviewed and approved.
That’s not a failure of certification. It’s a reminder that effective risk management requires multiple layers of oversight.
Respect the certification. Verify the activity. Monitor the frogs. 🐸
#MerchantRisk #Compliance #PaymentProcessing
I moved to LA in 2014 to build a social app. it failed.
I then built products for Kanye West and Rae Sremmurd, then took an engineering role in the 18+ industry.
the side quest became my career.
part 1 of how i accidentally got into payments:
gas stations realized the real money wasn't in gas. it was in everything sold around it.
payments is having its convenience store moment.
if you're just moving money and charging a fee, you're in trouble.
wrote about why payments companies are dying.
framerstacks$ retweeted
we've blocked 8.3% of gaming and prediction market transactions for geocompliance in the last 30 days.
that's nearly 1 in 12 transactions that might otherwise have been approved by a processor without the same location controls.
in regulated markets, knowing where someone is transacting from matters just as much as knowing who they are.
framerstacks$ retweeted
7 questions to test your payments stack:
How fast can you launch?
How much ops work is manual?
How many integrations do you maintain?
Can you see fraud in full context?
Can you add a payment method easily?
A new market?
Can you trace a payment end-to-end?
framerstacks$ retweeted
What is frameOS?
One operating layer for payments, onboarding, identity, fraud, disputes, billing, and payouts.
Most payment stacks aren’t built. They pile up one vendor at a time, until the hardest part is everything between the tools.
framepayments.com/blog/what-…
I got into payments basically by accident. I was working with an OnlyFans competitor doing hundreds of millions revenue, paying our processor ~15% per transaction.
the limitations of our processor forced me to learn payments from the ground up.
CCBill had no API. no fraud monitoring. no customer profiles. no stored payment methods. we ended up building our own fraud tooling because we had no choice.
I didn't know enough about payments back then to know if we could use a gateway like Authorize or NMI to improve the experience.
we sold video content, so we learned fast that videos not playing meant chargebacks. video infrastructure suddenly became a payments problem.
after paying 15%, this was our checkout experience. no Apple Pay. no address autocomplete. most users dropped off here lol
CCBill alone processes over billions per year.
but there’s a mountain of volume trapped with legacy processors in high-compliance industries. we plan to eat our way through that market on the way to Stripe.
we started building frameOS in January. ~90 days later, our first accounts were live.
six months ago we had 16 accounts. now we're over 60,000. processing volume driven by these accounts is up 895% in the last 60 days alone.
the idea behind frameOS is simple. compliance and financial services have operated in separate silos, despite being dependent on each other.
we built them into the same system.
an account can represent a user, business, or platform. each has capabilities to move money across cards, bank accounts, and wallets, which unlock as verifications like KYC, KYB, adverse media, and geo-compliance pass.
we're powering use cases across prediction markets, creator platforms, telemedicine, vertical SaaS, ISVs, and more.
compliance shouldn't sit alongside financial infrastructure. it should be part of the infrastructure itself.
greater access demands greater compliance.
we built AI-powered infra to continuously verify physician licenses, pharmacies, product offerings, and regulatory compliance.
we believe these controls belong directly in the payments layer. when something changes, the processor should be able to act.
compliance isn’t a one-time certification. it’s continuous enforcement.
so we built it.
🚨 BREAKING: TRUMP ADMIN PAVING WAY FOR TEMPORARY SALE OF CERTAIN PEPTIDES
SOURCE: WASHINGTON POST
$HIMS
launched payments and compliance infra for one of the largest festival aggregators and the biggest professional motorcycle road racing championship in the US this week.
event travel and ticketing is starting to become a meaningful vertical for Frame.
our underwriting team and Ralfi (our AI underwriter homie) apparently have a very diverse taste in entertainment
maybe we’ll see a furry convention next?
The experience from stripe here is terrible because there is actually a pretty obvious reason this merchants account was paused and stripe could have communicated this too them and allowed them to edit there site before closing there account…..
If you go check out the actual site there’s a bunch of copyright infringing content on the site that they don’t have proper licensing to be selling from what I can see.
If they do have licensing and they missed it lmk
Stripe can shut down your business in one email and then refuse to tell you what you actually did wrong.
That’s exactly what happened to us.
MacWall had:
• thousands successful payments
• ONE $3.99 chargeback
• real software + real customers
Then @Stripe suddenly closed our account for vague “business model risk.”
Since then:
• 5 days waiting
• 10+ emails
• multiple support chats
• full compliance + policy cleanup
• documents offered
• formal complaint submitted
And still no specific violation. No actionable explanation. No real answer.
Meanwhile payouts are frozen and legitimate customers are being refunded i am not asking Stripe to expose some secret fraud algorithm.
Just tell us what MacWall actually did wrong.
If we violated a policy, name the policy.
If something needs fixing, tell us what to fix.
If the risk system made a mistake, have a human review it.
A payments company this important should not be able to destroy a small business relationship with a vague sentence and then disappear.
@stripesupport @Stripe we need an actual answer.
Indie founders deserve better than this.
As agents become more prevalent in payments the real probably is who’s at fault in the case of a chargeback.
There isn’t a universal verifiable way to tie an agent to its owner, though @google & @stripe seems to have come out with agent protocols for identity are promising. An agent doesn’t show its id before it makes a purchase on your behalf, it simply just completes the purchase on your behalf with your info.
Which is essentially fraud in the eyes of a card brand as there isn’t a way to prove you authorized that purchase yet, or at least as far as I’m aware of, but if I’m missing something correct me.
I digress
You could certainly follow a data trail and reasonable assume an agent may belong to an individual but there isn’t a confirmation…yet
What if there was a verifiable way to who an agent belonged to? This would certainly help with the future agent dispute problem that may be coming to retailers soon with the rapid adoption of agents like instinct
With all the legislation aimed at Prediction Markets this is likely the type of product they’d need to start adapting to make regulators feel more comfortable for allowing gambling in there state.
People have to remember now individual states have the power to regulate what a prediction market does in a given state
If a prediction market we’re able to quantifiably say that there users aren’t being irresponsible using metrics I think that they’d like this and it would increase the likelihood a given prediction market gets free operating in a given state
At @frame_payments we believe in providing compliance tooling that unblocks high compliance merchants to process payments freely
Would you be interested in frame guard ?
the struggle described in this piece makes sense. as a founder, your instinct is to remove friction and grow. I think there's a happy medium between being overly sensitive to risk and being reckless about it.
prediction markets are a unique fraud surface because a win pays out in cash. we process payments for one at Frame and see the same patterns. stolen cards, card testing, velocity attacks, etc.
we think the approach should be to push verification upstream. we combine device signals, KYC, $0 3DS auth, card/address name matching, and more into onboarding to tie the user to the payment method before they transact.
this is what a good UX looks like…verification happens before the first transaction so you have fewer actual fraud losses (friendly fraud is another story).
wsj.com/business/polymarkets…
to be clear, anyone of any race can be named Laderian. the man in this ID photo is certainly not... Laderian.
this is the kind of tacit knowledge that’s hard to train into a risk model. sometimes everything technically passes, but a human looks at it for three seconds and knows something is off.
at @frame_payments , our underwriting models recommend decisions, but a human still confirms them before we set a customer live. human-in-the-loop still matters a lot in risk.



















