A bill-splitting app that says it has a Venmo integration is making two different promises, and only one of them is the app’s to keep. An in-app integration is a permission: the app calls a Venmo interface that Venmo granted, and Venmo can narrow, re-scope or withdraw that interface without asking. A payment link is a public address: a URL anyone can type, built to a shape Venmo published, that a phone can hand to the Venmo app or open as a web page. The first promise can fail inside someone else’s product with nothing for the payer to see. The second degrades in the open. For a group split, the only thing that matters is whether each person’s amount and note arrive in the payer’s app intact, and the two designs fail that test in very different ways.
The gap is not theoretical. In February 2016, Venmo’s developer site was changed to read “The Venmo API is no longer available,” then the company clarified that the API stayed open to existing developers but closed to new ones. By 2025 its developer page carried a notice that the Developer and Payouts APIs had been retired for businesses that did not already have access (archived 2025-08-04); that address now redirects to a Venmo for Business page. Meanwhile, on 9 October 2026, a link built to Venmo’s own payment-link documentation, with a username, an amount and a note, still resolved to Venmo’s current payment-link address with every parameter in it carried through. Two recent App Store reviews of one bill-splitting app mention trouble with its Venmo feature. Those reviews are colour, not proof. The record is about access, not uptime: Venmo denied the interface to new apps and, per TechCrunch, said it might remove features from the old one; we did not watch an existing integration break, and our link test recorded a redirect, not a completed payment. The argument is about which promise an app can keep.
Sources: TechCrunch, 2016-02-26, and PYMNTS, 2016-02-29, for the 2016 closure and the 2010 start; Venmo’s developer page (archived 2025-08-04) for the retirement notice; the redirect count is our own test on 2026-10-09; the review count is ours, from Apple’s most-recent-reviews feed for Tab, read the same day.
What is the difference between a payment integration and a payment link?
An integration is code inside one app that talks to another company’s system through an interface that company controls. The app needs credentials, the interface has terms, and the platform decides who gets access and what the access does. In the research on software platforms, these interfaces are called boundary resources: the APIs, kits and rules a platform owner publishes so outsiders can build on it. Ghazawneh and Henfridsson, in a 2013 paper in the Information Systems Journal, model their design as a balance of two drivers, resourcing (handing capability to third parties) and securing (keeping control of the platform), and name “sovereignty securing” and “regulation-based securing” among the moves owners make. Securing is the half that matters to a bill-splitting app: an integration exists at the pleasure of the platform. One hedge before going further: Venmo itself uses the word loosely. Its archived developer page describes Splitwise sending users “straight to the Venmo app” as “Venmo’s simple integration,” so the two-way split in this article, permissioned interface versus public address, is our taxonomy, not Venmo’s.
A payment link is a different object. It is a web address with the payment written into it. Venmo’s own documentation for payment links described the shape: a username as the path, then query parameters for the transaction type, the amount and the note. On a phone, that address does not need a Venmo API at all. Apple’s developer documentation on universal links describes the general mechanism: because they are “standard HTTP or HTTPS links, one URL works for both your website and your app,” and “if the person hasn’t installed your app, the system opens the URL in their default web browser.” Only the website owner can store the file that authorises the association, so whether a venmo.com address opens in the Venmo app is Venmo’s choice, and we did not test it. What the app that generates the link does not need is permission: it is addressing a public page.
Code in the splitting app calls an interface Venmo granted. Needs credentials and continuing approval. When the interface changes, the button in the app stops doing what it did, and only the app’s developer can repair it.
A URL carrying the recipient, amount and note. Needs no approval to create. A phone can hand it to the Venmo app or open it as a web page. If the shape changes, the page can still load, and the payer can see what did or did not arrive.
By design, not by test: a failed integration call can leave the payer with no request at all, while a link lands the payer on a Venmo page that either carries the amount or does not. Either way the fallback is the same, the amount sent in a message; the difference is who notices, and when.
Sources: Ghazawneh & Henfridsson, “Balancing platform control and external contribution in third-party development: the boundary resources model,” Information Systems Journal 23(2), 2013; Apple Developer Documentation, “Allowing apps and websites to link to your content”; Venmo Payment Links documentation, archived 2024-05-07.
What happened to Venmo’s developer API?
It was offered, then closed to newcomers, then retired for new businesses. PYMNTS reported in February 2016 that Venmo “had initially started pushing its API on developers in 2010.” TechCrunch reported on 26 February 2016 that “this month Venmo suddenly changed its dev site to read ‘The Venmo API is no longer available,’” and that the company had just recorded “$1 billion transferred” in January. Venmo then issued a correction, quoted by both outlets: “The Venmo API is still available to existing users, however we are not offering access to new users. We apologize for the confusion created by the ambiguity in our prior statement.” Both reports tied the move to Pay with Venmo, a product for paying businesses, which PYMNTS described as a newly launched beta. Venmo’s own statement spoke of “a new feature that allows users to potentially pay merchant apps with Venmo.”
The retirement notice is the important line. What a platform granted in 2010 it narrowed in 2016, and by the time of the 2025 capture it had retired the API for any business that did not already hold access; the same notice says businesses granted access in the past, “generally prior to 2016,” retain it. The notice sent businesses that want Venmo in their checkout to Venmo’s business pages. One documented route is Braintree, which processes Venmo payments “through your Braintree integration” and limits them to merchants: “You can use Venmo for payments only with United States-based business entities.” A friend paying a friend their share of dinner is not a merchant checkout, so for a consumer bill-splitting app the integration route is closed for new entrants.
The lesson from 2016. TechCrunch’s 2016 piece opened with “This is not how you run a platform. Developers remember.” Ten years on, the memory that matters belongs to users: an app whose Venmo button depends on an interface the platform no longer issues to new entrants has a feature that a new entrant cannot rebuild if it breaks.
Sources: Josh Constine, TechCrunch, 2016-02-26; PYMNTS, 2016-02-29; Venmo developer page, archived 2025-08-04; Braintree, Venmo overview, read 2026-10-09.
What does platform research say about interfaces like this?
That the interface is the owner’s lever, and that the owner keeps adjusting it. The closest study is Eaton, Elaluf-Calderwood, Sørensen and Yoo’s 2015 paper in MIS Quarterly on Apple’s iOS. Analysing 4,664 blog articles about 30 boundary resources across six themes, they found that these resources “are shaped and reshaped through distributed tuning,” which involves “cascading actions of accommodations and rejections of a network of heterogeneous actors and artifacts.” Their abstract adds that the study “also shows the dualistic role of power in the distributed tuning process.” Our reading, not the paper’s wording: the owner can accommodate an outsider’s push, and it can reject it. An API is not a fixed thing an app builds on. It is a setting that keeps being adjusted, by the owner and by the network around it, and an app on the outside experiences those adjustments as features appearing and disappearing.
Kevin Boudreau’s 2010 paper in Management Science separates two ways of opening a platform. Studying 21 handheld computing platforms from 1990 to 2004, he distinguished granting access to a platform from giving up control of it. Granting access to outside hardware developers produced “up to a fivefold acceleration in the rate of new handheld device development.” Where owners went further and devolved control, the extra effect “was still positive but an order of magnitude smaller.” The domain is handhelds, not payments, and the paper reports innovation effects rather than owner motives, so this is an analogy we draw, not a finding about Venmo. Our reading of it: most of the measured gain came from granting access, and an owner that grants access can also withdraw it, as Venmo did in 2016. A payment API is access. A public URL is closer to something nobody has to grant.
Sources: Eaton, Elaluf-Calderwood, Sørensen & Yoo, “Distributed Tuning of Boundary Resources: The Case of Apple’s iOS Service System,” MIS Quarterly 39(1), 2015; Boudreau, “Open Platform Strategies and Innovation: Granting Access vs. Devolving Control,” Management Science 56(10), 2010. Quotations are from the published abstracts.
What does a Venmo payment link actually carry?
Everything a split needs, in plain text. Venmo’s developer site documented a payment link as a username path followed by a handful of query parameters, with examples that read like a dinner table. The documentation page itself is gone from its original address (it now redirects to a Venmo for Business page), but the Internet Archive holds a copy captured on 7 May 2024, and the parameters below are taken from that capture.
Note the last documented example: “Charge multiple recipients for dinner,” with a $23.25 amount and a note that says “for dinner.” Venmo wrote the bill split into the specification. Any app, spreadsheet or person can produce that address with string concatenation, and the string carries the per-person amount and the reason for it. There is no credential in it, so there is no per-app permission for a platform to revoke, and nothing the generating app has to keep alive. What Venmo does keep is control of how its servers and its app treat the parameters, which is the limit the next section tests. The shape was documented, and the documentation was public.
Source: Venmo, Payment Links, developer documentation archived 2024-05-07. Examples are Venmo’s own.
Does the link still work now that the documentation is gone?
On the day we checked, the address still resolved. On 9 October 2026
we requested
venmo.com/kortina?txn=pay&amount=1.25¬e=test
from a US network. It redirected twice and landed on
account.venmo.com/payment-link?amount=1.25¬e=test&recipients=kortina&txn=pay
with HTTP 200. The host changed, the route changed, and every
parameter in the link we sent (recipient, transaction type, amount
and note) was carried across to the new address. We recorded the
final URL and status code; we did not open the page in the Venmo
app. The same day, venmo.com/paymentlinks, the
address of the documentation itself, redirected to a Venmo for
Business marketing page.
That is the asymmetry in one test. Venmo took down the page that explained the link and kept routing the link to its payment page. It retired the developer API for every business that did not already have access. Venmo has not said why, and a redirect test cannot tell you; the two decisions are the record.
The honest limit. A public URL can change too; Venmo moved its payment page to a new host, and it could drop a parameter tomorrow. The difference is not that links never break. It is where the failure is likely to land: a link addresses a Venmo page, so a broken one is more likely to leave the payer somewhere visible than a failed call inside another app, and nobody needs Venmo’s permission to compose the next link. We reason that from the two designs; we have not tested a failure, one check on one day is a snapshot, not a guarantee, and the organiser’s fallback, the amount sent in a message, is the same either way.
Source: our own redirect check, 2026-10-09 (requested and final URLs recorded verbatim); Venmo Payment Links documentation, archived 2024-05-07.
How do the two designs fail, side by side?
Two reviews of Tab, a bill-splitting app in the US App Store, show what a user sees when an advertised Venmo feature does not work for them, and nothing about which design is behind it. We cannot see whether Tab’s Venmo feature is an integration or a link. A reviewer on 20 August 2026, under the title “No Venmo Integration and can’t handle large bills,” wrote: “I can’t figure out for the life of me how to setup the Venmo integration that is referenced in the description and FAQ.” That is a setup complaint, not a report of a breakage. Another, on 14 September 2026, five stars, wrote: “For some reason the Venmo plug-in doesn’t work with this app at the moment, but that’s an easy enough work around.” We cannot see Tab’s code, and two reviews are not evidence of a cause. What the second reviewer describes is the experience the table is about: a feature not working for them, and a user who could not tell why. The reviewer does not say what the workaround was.
Sources: Apple App Store most-recent customer reviews feed for Tab, read 2026-10-09 (reviews dated 2026-08-20 and 2026-09-14, both on app version 3.128.0); Braintree, Venmo overview.
What should you check before trusting an app’s Venmo button?
The feature claim “has Venmo integration” tells you nothing about which of the two designs is behind it or whether it still works. Four quick checks settle it at the table, before the group relies on it.
Try it before the bill comes
Tap the app's pay or request action for one person. What opens tells you little on its own, since more than one design can switch to the Venmo app. The test is what arrives: a Venmo screen that already shows that person's share and a memo naming the dinner. If either is blank, the handoff lost data, and the payer will have to type the number, which is a chance for the split to drift.
Ask for the address
If the app can show or copy the request as a link, look at it. A venmo.com address with the transaction type, amount and note written into it is the public shape Venmo documented, and you could send it by text yourself. A request you cannot see as an address gives you nothing to fall back on if the button stops working.
Check the date
Any roundup or comparison that lists Venmo integration as a feature is describing a day in the past. Look for the app's last update and whether reviewers from the last few months mention the Venmo path. Venmo closed its developer API to new apps in 2016 and its developer pages carried a retirement notice by 2025; a feature table without a date cannot reflect that.
Keep a copyable amount
Whatever the app does, make sure each person's share exists as a number they can copy. A link embeds it; an integration may not expose it. If the button fails, the group should be able to fall back to a message with the amount in it, not to a shrug.
splitty sends each person a pre-filled payment request; it does not run the payment itself. For Venmo that request is a deep link; for Monzo, PayPal and Revolut it is a share link; for Cash App and the regional methods it is copy-and-open. In every case the per-person amount travels with the request, and in every case the payer finishes in their own payment app. Share Split is a web link the recipient opens to pay via their own preferred method, without the app, so only one person at the table needs splitty at all. For the hands-on version of a Venmo payment link, see how to share your Venmo link with an amount attached; for what to do when a rail is down altogether, see backup strategies for payment app outages.
FAQ
Venmo integrations and payment links: quick answers
01 Why does a bill-splitting app's Venmo integration stop working?
The public record does not show Venmo breaking an existing app's button, so we cannot name the cause in any one case. What it shows is who controls the fix. Venmo closed its developer API to new apps in February 2016, TechCrunch reported it might remove features from the existing one, and by 2025 its developer page said the Developer and Payouts APIs had been retired for businesses without existing access, while those granted access before 2016 kept it. An in-app integration is a permission the platform can narrow or withdraw; if a button built on one fails, only the app's developer can repair it, and a new entrant cannot get the access at all.
02 What is a Venmo payment link?
A venmo.com web address with the payment written into it. Venmo's own documentation described a username as the path and query parameters for txn (pay or charge), amount, note, recipients and audience, with 'charge multiple recipients for dinner' as one of its examples. Apple's documentation describes a configured universal link opening in the app when it is installed and in the browser otherwise; we did not test Venmo's routing, only that the parameters survived the redirect. No API is involved in composing the address.
03 Can I still use Venmo payment links with an amount and note?
On 9 October 2026, a link in the documented shape (username, txn=pay, amount, note) redirected twice and landed on Venmo's current payment-link address with the recipient, transaction type, amount and note carried through in the URL, even though the documentation page itself now redirects to a business marketing page. That was a redirect check on one day, not a test inside the Venmo app and not a guarantee; it is the behaviour a public URL contract tends to show.
04 Is a universal link the same as an API integration?
No. An API integration is code that calls the platform through an interface the platform granted, with credentials and terms. A universal link, in Apple's words, is a standard HTTP or HTTPS link where one URL works for both the website and the app, and if the person hasn't installed the app, the system opens the URL in their default web browser. Anyone can write that URL; no credential from the platform is needed to generate it. Whether a venmo.com address opens in the Venmo app is Venmo's configuration, which we did not test; our check recorded only that the parameters survived the redirect.
05 How does splitty send each person's share to Venmo?
splitty sends each person a pre-filled payment request in their preferred payment app. For Venmo that is a deep link; for Monzo, PayPal and Revolut a share link; for Cash App and regional methods, copy-and-open. Share Split is a web link the recipient opens to pay via their own method without the app. In every case the per-person amount travels with the request, and the payer finishes in their own payment app.
