UniwebPay Skill
Financial Infra for the AI era
193 followers
Financial Infra for the AI era
193 followers
Accept payments the moment you ship. UniwebPay Skill is the financial infrastructure for the AI era, helping builders turn AI products into businesses. Generate payment links, accept global payment methods, and start getting paid without the usual payment setup, merchant onboarding, or infrastructure overhead.
Free
Launch Team
Render: Get up to $100K in startup creditsCloud infrastructure for founders who want to move fast and NOT break things
Promoted
@uniwebpay nice launch.. congrats for shipping today
The frustrating part of payments is the thing you have removed, so the useful question is where it went rather than whether it is gone.
Onboarding and KYC take days because somebody has to be accountable for who is collecting money from the public. That requirement does not disappear when the integration gets faster, it moves. So which is it: are you the merchant of record with builders sitting underneath you as sub-merchants, or is the KYC deferred rather than removed? Both are legitimate and they fail very differently. If it is deferred, the moment it lands matters enormously, because finding out you cannot withdraw after taking real money from real customers is a much worse problem than a slow start.
The related one is termination. If you are the merchant of record then my ability to keep collecting depends on your risk appetite, not mine. What does notice look like, and what happens to funds in flight? Nobody asks that until it has already happened to them.
Second thing, and it comes from this being a skill rather than an API. A payment link is a request for money in my name. If an agent can generate and send one, the failure is not a bad log line, it is a wrong amount, a wrong currency, or a description a customer reads on their statement and does not recognise. And it is quiet, because they either pay or they do not, and neither outcome tells me something went wrong. Is there a point where a human sees the amount before a link leaves, or is that entirely left to whoever installs the skill?
@dalemooney Love this! You basically did our risk-review homework for us in one comment. KYC deferred vs. removed, and a payment link as a silent failure mode... that's exactly the right lens.
Here's where we actually stand:
Human review before a link goes out?
We ship both a Skill and a full API — the Skill is just a thin wrapper on top. Straight out of the box with the Skill, no forced review step. But if you build on the API directly, you can slot in your own approval/validation before the link actually fires. So it's not baked in — it's available to whoever wants to own that control.
KYC — deferred or gone?
Deferred, not gone. We're licensed in Singapore. You can build and ship fast, but KYC kicks in right before withdrawal, not at signup. So you get the fast start without the "surprise, you can't cash out" problem — you'll know exactly when that gate is coming.
The setup lag is what kills the 'just try it' window. We run experiments adding paywalls to new features, and merchant onboarding turns that into a multi-week detour before we even know if users will pay. One question on the global side: when you say 'accept global payment methods,' does that include the payout leg, or mainly acceptance? Outside the US that's usually the harder half.
@hazy0 That "just try it" window is exactly what we're optimizing for. A multi-week onboarding detour before you even know if a paywall converts defeats the point of experimenting in the first place. That's the whole reason we're pushing the deferred KYC model: get the paywall live today, only deal with the compliance step once someone's actually trying to pay.
On the global question, good catch, and you're right that acceptance is the easy half.
If there's a gap between the two (you can accept payment in a market before you can actually pay a merchant out there), that's worth stating plainly rather than letting people find out at withdrawal time, same principle as the KYC timing point above.
Payment links solve the getting-paid problem, but the thing that bites later is reconciling what the skill says you earned against what actually lands in your bank account once fees, currency conversion, and chargebacks are netted out. Is there a ledger or export a builder can pull directly, or does that reconciliation work fall on whatever accounting tool they bolt on afterward?
It still feels surreal that you have a solution to such a complicated process. Can I use it for USD ? Open for options here
I like agent-native payments. The metric I’d eventually want is payment + AI cost per successful task, including retries. Agents can automate work and automate surprise invoices equally well.