UniwebPay Skill

Financial Infra for the AI era

Fintech

Payments

Artificial Intelligence

Visit WebsiteSee on Product Hunt

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

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?

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.