To collect from a diaspora: card via Stripe covers the bulk — members living abroad have a card and pay online, regardless of their country. The real constraint is the association's country (the collection account must be in a supported country, France for example), not the member's. Mobile Money (Wave, Orange Money, M-Pesa) remains necessary for members who stayed in the country of origin and are unbanked, via a local relay. You then adapt the pricing to the country of residence, automate reminders, and rely on fund transparency for trust.
Can you collect diaspora dues from abroad?
Yes. A member can pay online from any country as long as they have an accepted method — most often a card. The real constraint isn't the member's country, but the association's.
This is the most common misunderstanding. People think a diaspora is hard to charge because members are "abroad." In reality, accepting a card payment doesn't depend on the payer's country: a card issued in Canada, Senegal or Germany works on an online payment page. What must be in a supported country is the association's collection account. With a provider like Stripe, available in over 40 countries, an association registered in France opens an account without difficulty, and funds are paid directly into it. Concretely: if your association is French, you can collect dues from members spread around the world starting today. You just need to know who your members are — collection assumes a prior registry.
Card, Stripe or Mobile Money: which payment method for a diaspora?
For members living abroad, card via Stripe covers the bulk of dues. Mobile Money remains essential for members who stayed in the country of origin and are unbanked — but it requires a local relay, since it isn't natively handled by a European merchant account.
The right way to think about it is to segment the community by place of residence, because payment methods differ.
- Members in developed countries (France, EU, North America…): they have a bank card. Card, complemented by Apple Pay, Google Pay and SEPA direct debit in Europe, covers almost every case. This is where most of a diaspora's dues volume sits — so it's the foundation to get right first. Stripe handles all of this as standard.
- Members who stayed in the country of origin, notably in Africa: the banking rate is lower and Mobile Money (Wave, Orange Money, M-Pesa) is often the dominant payment method there. But these rails aren't natively supported by a European merchant account. For this segment, you need a local relay: a person or a chapter on the ground collects via Mobile Money then remits in a consolidated way, and the admin records these payments in the platform to keep a single view.
Honesty on this point is what sets a serious project apart: announcing "Mobile Money integrated" when you actually collect by card creates disappointment. The right promise is: online card for the diaspora, Mobile Money relay for the field, and a single base that reconciles the two. The other technical pitfalls of a diaspora project (hosting, time zones, authentication without a French phone number) are detailed in the 7 pitfalls of a diaspora platform.
How do you handle several currencies and the purchasing-power gap?
You display the amount in the member's currency when possible, and above all you adapt the pricing to the country of residence: the same sum can be heavy from one country and symbolic from another.
Two distinct problems hide behind "currency." The first is technical: a member prefers to see and pay in their own currency. Stripe can present and charge in several currencies, the funds then being converted and paid out in the currency of the association's account (conversion fees apply — to factor into the pricing, not to discover after the fact).
The second problem is more strategic: the purchasing-power gap. Dues of €50 are trivial for a member based in Geneva and prohibitive for a member living in Bamako. Imposing a single worldwide amount mechanically excludes part of the community — often those who stayed in the country of origin, precisely the most attached to the bond. The answer is a tiered scale by zone: dues tiers indexed on the country of residence, or even a "pay what you can" formula (free amount above a floor) that lets everyone contribute to their means. The goal isn't to maximize the average ticket, it's to maximize the participation rate.
How do you set the amount of diaspora dues?
You start from a simple, readable scale, indexed on the country of residence and on the benefit delivered, rather than a round number decided in an assembly with no reference.
The principles that hold: a small number of tiers (two or three are enough — for example residents of developed countries / residents of the country of origin / reduced rate for students and retirees); an amount tied to a concrete benefit (access to the member map, to events, to mutual help) rather than to a vague "membership"; and an annual payment by default, simpler to follow up than a one-off. The fine mechanics of pricing, payment methods and reminder sequence are shared with alumni networks: the 2026 dues benchmark details scales and a reminder sequence that clearly improves the collection rate, transferable to a diaspora.
How do you raise the payment rate (reminders)?
By automating a multi-channel reminder sequence instead of chasing each member by hand: it's the top lever for payment rate, far ahead of the amount.
Manual collection — email then WhatsApp then individual follow-up — is the default mode for diasporas, and it's also why the payment rate plateaus: the volunteer burns out before having reminded everyone. An automated sequence changes the scale: an initial call for dues, then two or three spaced reminders to non-payers only, with a direct payment link (not an IBAN to copy out). The short-message reminder (WhatsApp/SMS) works particularly well in diasporas, where these channels are more read than email. Finally, you target: reminding those who have already paid is the best way to annoy them. If part of the community no longer responds at all, the re-engagement logic is the same as for a dormant network — you first have to give a reason to care again before asking for money again.
Receipts, fund transparency and GDPR: what to plan for?
The tax receipt depends on the association's status and the donor's country; but for a diaspora, the number-one issue isn't fiscal, it's transparency: showing where the funds go.
On the fiscal side, let's stay precise: only certain public-interest associations can issue tax receipts, the benefit depends on the contributor's country of residence, and dues don't open the same rights as a donation. To frame with your accountant according to your status — don't promise a tax benefit by default.
What weighs most on a diaspora's dues rate, however, is trust. Members sending money from abroad want to know it arrives and what it's for. A diaspora that has already seen an opaque fund end badly pays all the less. The concrete lever: a visible tracking of collected amounts and their use (how much raised, for which project, where things stand), accessible to members. Transparency isn't a nice-to-have, it's a collection argument. On the data side, finally, collecting payments adds personal information to manage: the framework is the same as for the rest of the base, detailed in the GDPR guide for a diaspora platform. For the full collection mechanics and the member map, see Terrilink for Diaspora.