Today we're launching support for Natural in Agent Pay. Businesses on Linq can now create a Natural wallet directly from the admin panel, and request and receive payments from their users over iMessage, settling into that wallet. It works alongside the Stripe rail Agent Pay launched with, through the same API, with one new parameter.
Why we built it
Agent Pay has always settled directly to your own Stripe account. That model is right for a lot of businesses, and it isn't going anywhere. But it asks something of you: a Stripe account, Stripe's verification, and the responsibilities of being the merchant of record.
A growing share of what's built on Linq doesn't fit that shape. Teams are shipping agents that hold funds, businesses want to collect over text without operating a payments stack, and money is starting to move between parties that are software. Natural was built for exactly this: custodial wallets with verified identities, audit trails on every transaction, and an API designed for automated money movement. Pairing it with iMessage means the request for payment shows up in the same thread where the conversation already happened, from a number the payer already knows.
How it works
Onboarding starts in the Linq admin panel. Your payments settings now include Natural onboarding; completing it verifies your business and creates your wallet. Requests you create through Linq show up there, and your balance, payouts, and the rest of your wallet activity live in your Natural account, with the Natural dashboard giving you wallet-level visibility.
Once you're onboarded, collecting a payment is one API call. Set rail to natural, address the payer by phone number, and send from a line your organization owns:
curl -X POST https://api.linqapp.com/v3/payment_requests \
-H "Authorization: Bearer $LINQ_API_KEY" \
-d '{
"rail": "natural",
"amount": 4000,
"currency": "usd",
"from": "+14045550132",
"payer_handle": "+14155550178",
"description": "Training session, July 24"
}'
The request lands in your user's Messages thread. They pay, the funds settle to your wallet, and you get the same payment.succeeded webhook you already handle, so your reconciliation code works unchanged.
Built on verified identity
A payment request in a text thread is only as good as the payer's confidence in who sent it. Every organization collecting on the Natural rail completes Natural's business verification before it can charge, every wallet is tied to a verified legal entity, and every request is sent from a line your organization owns. Every transaction carries a full audit trail on both sides.
Get started
Natural onboarding is available today for every organization, in the payments settings of the admin panel. Complete verification, send your first request with rail: "natural", and you're collecting over iMessage. The payment rails documentation covers both rails in depth.
We believe the thread is where more and more business will get done, and payments belong where the conversation is. This launch closes the gap between the two.
