It's all in the language.
If you want to encourage your users to donate, explain all preconditions at once, thus definitely idea 1 over idea 2, especially if Stripe availability is a potential stumbling block. Do not disclose piecemeal here.
That aside, use brief, directive, and encouraging phrasing. Like so:
"To publish this page, upgrade your account and connect to Stripe".
Two or three actions in a notification is not too much to process if the grammatical structure of your sentence conveys its action-condition structure with clarity. Hence, list the presumed goal first ("To publish..."), followed by enumerated directives ("upgrade [so-and-so]" and "connect [to so-and-so]").
A phrase that starts with "You cannot...", while perhaps a technically accurate reflection of the underlying code structure, is an immediate deterrent: I'll pay much less attention to whatever reasoning might follow. By the time I get to the "until..." part, this has me thinking 'please don't fuss, just tell me what to do and let me get on with it'. If another obstacle is then presented to me in a second, afterthought-style sentence ('oh, by the way, you also need...'), that has me wonder what other potentially unfulfillable conditions lurk further beneath.
Nah, I'm losing interest!
Therefore "To [goal verb + object], [action verb 1] + [action object 1] and [action verb 2] + [action object 2]": The goal is immediately named, thus attainable, and here's how you'll get there... do 1, then 2,(and then 3). Presto.
As to the availability of Stripe in some countries but not others - is there a way of ascertaining this from the user's/server's IP address? If your user cannot connect to Stripe due to location, the option to publish basically cannot be fulfilled and should not be offered to them. If we lead them down an experimental path only to unearth frustration, that will leave a bad taste.
One way to test this manually is to add a system check affordance to the 'Donate / Publish' (?) notification; add "Check Stripe availability" as a link button.
Alternatively, certainly less ideal, you could prefix a country selection to the whole control set by which you upgrade your account in the interest of publishing. That could filter out the upgrade option altogether, so you won't be presented with an option you likely cannot take advantage of.
The Stripe dependency is ultimately more of a business model cul-de-sac than a problem solvable by UX or labelling language: The whole offering seems to be somewhat reliant on a third-party service, and some audience segments are at the mercy of that service's availability. Since I'm a bit of a stickler for roles and responsibilities first, and collaboration among them next; what does the product manager have to say about the Stripe dependency decision?
