Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
strnisa
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
1.
▲
by
strnisa
3mo ago
Founder of Unattach here. Just to clarify: Unattach does not corrupt or mangle emails. Because Gmail does not expose an API for modifying the original email in place, Unattach creates a new version of the email with attachments removed/
2.
▲
by
strnisa
7mo ago
It seems to me that major US cloud companies are using politics to try to get more value from non-US data, which I believe will push the EU (and others) to accelerate the move to their own alternatives. This is another move that seems to sa
3.
▲
AI-calls-Editor: IDE-native refactoring for AI coding assistants
(blog.strnisa.com)
7 points
by
strnisa
10mo ago
|
0 comments
4.
▲
by
strnisa
1y ago
From what I can find, Gripto was a cryptocurrency platform for viewing holdings, market info, and relevant news. It seems that the service was retired in late 2018.
5.
▲
by
strnisa
1y ago
Flattr was a micro-donation subscription service where users set a monthly budget that was allocated to creators. Small Transfers is for usage-based billing of online services and APIs. There is no monthly budget, wallet, or pre-funding. Cu
6.
▲
by
strnisa
1y ago
BLIK is a bank-backed payment method used at checkout. Small Transfers is an API for a merchant to charge a customer tiny amounts (as little as $0.000001), which are batched into a single card charge via Stripe.
7.
▲
by
strnisa
1y ago
If a customer's balance is under $1 at the end of the month, we delay charging them for up to 60 days and send email reminders. If it's still under $1 after 60 days, we charge at least $0.50 and credit the difference (after fees)
8.
▲
by
strnisa
1y ago
Customers do create an account and provide a payment method, but they don't pre-fund or hold a balance, and they don't initiate a payment. Small Transfers is an API that allows merchants to charge very small amounts programmatical
9.
▲
by
strnisa
1y ago
I'm working on Small Transfers ( https://smalltransfers.com/ ), a payment platform that makes it very convenient for SaaS / API makers to provide a pay-as-you-go model to their customers. You can charge as little as
10.
▲
by
strnisa
1y ago
I understand not wanting another subscription. You can subscribe and then immediately turn off auto-renewal — your access stays active for the full year you paid for. On PAYG, you can target the largest emails first and stop whenever you&#x
11.
▲
by
strnisa
1y ago
You're correct that this adds a barrier to entry, but for many users, that hurdle is still lower than asking them to start a subscription or buy a prepaid bundle. We plan to provide the classic "Google Sign-In" style pop-up w
12.
▲
by
strnisa
1y ago
I misunderstood this comment originally. In principle, Small Transfers (ST) could let a content site bill AI agents per request. Each site (acting as an ST merchant) would expose a simple "content" endpoint. The AI agent (as an ST
13.
▲
by
strnisa
1y ago
That's an interesting idea. This may avoid the e-money issues, but: - The customer has to pay upfront, which lowers conversion rates. - No shared balance across multiple merchants, resulting in higher total payment processing fee
14.
▲
by
strnisa
1y ago
The key legal issue is interchangeability. Single-merchant vouchers are generally acceptable. If a voucher can be used across multiple merchants, it's often treated as e-money in the EU. Not being able to use funds across multiple merc
15.
▲
by
strnisa
1y ago
I see what you mean — yes, this could be useful to some customers. We already implement a small grace amount above the max-owed limit that allows for continued service; your idea would essentially allow the customer to increase the default
16.
▲
by
strnisa
1y ago
The primary objective of the max-owed limit is to cap per-customer risk. If you are suggesting that the max-owed limit is actually N×X, then that would multiply worst-case exposure by N, which is undesirable. If you are suggesting that we c
17.
▲
by
strnisa
1y ago
Authorization hold periods are set by the card networks/issuers and by merchant category, not Stripe. Even if longer holds were possible, using authorization holds as a prepayment proxy can raise regulatory/consumer-protection iss
18.
▲
by
strnisa
1y ago
Each customer already has a limit on the amount they can owe before we require payment. Each customer account also requires a unique payment method, which must pass Stripe Radar and 3-D Secure checks. We plan to add more checks in the futur
19.
▲
by
strnisa
1y ago
We don't hold upfront funds. When a customer pays, we initiate Stripe transfers to the merchant as soon as the funds are available. Paying the merchant before the customer's card payment settles would mean advancing funds, which w
20.
▲
by
strnisa
1y ago
Yes, merchant abuse is a risk. What we do and plan to do: - Each merchant requires an OAuth grant, and customers can revoke it at any time. - A customer ledger shows what, when, and how much each merchant charged. This can be shown in
21.
▲
by
strnisa
1y ago
Subscriptions are great for predictability, and most apps should keep them. Small Transfers can be added to help with: - users who dislike subscriptions - infrequent users - reducing/removing free-trial costs for non-converting
22.
▲
by
strnisa
1y ago
Online card holds typically expire in ~7 days (often sooner, depending on the issuer), which is too short for our use case.
23.
▲
by
strnisa
1y ago
x402: on-chain, HTTP 402, wallet-to-server, synchronous per-request payments. Small Transfers: card rails (Stripe), account-based, off-session, batched billing with spend caps; no tokens/wallets.
24.
▲
by
strnisa
1y ago
Definitely! The API lets you authorize the maximum your AI request might cost (+ margin), then capture the actual cost (+ margin). For some example code, see our Next.js Starter project: https://github.com/smalltransfers
25.
▲
by
strnisa
1y ago
That approach generally doesn't work from a legal perspective: prepaid tokens are often treated as e-money (especially if it's not for company's own products or services), and in many jurisdictions, holding value for users re
26.
▲
by
strnisa
1y ago
We run Stripe Radar and 3-D Secure when adding a card (before first use), which filters out a lot of obvious fraud (and 3DS often shifts liability to card networks in many regions). The balances are not settled just at the end of the month.
27.
▲
by
strnisa
1y ago
If you store funds for a specific service that you provide, it's fine. If it's for many services or services provided by others, it's legally problematic.
28.
▲
by
strnisa
1y ago
If a customer's balance is under $1 at the end of the month, we delay charging them for up to 60 days and send email reminders. If it's still under $1 after 60 days, we charge at least $0.50 and credit the difference (after fees)
29.
▲
by
strnisa
1y ago
Requiring money upfront would classify the platform as an e-money institution, which is highly problematic from the legal perspective.
30.
▲
by
strnisa
1y ago
Nice work and thank you for the encouraging words!
More ›