Outreach templates
Short first emails for banks, processors and pilot merchants, plus the follow-up sequence. Adjust the bracketed parts; keep the length.
Bank partnership, first email
Subject: Platform payments partnership in [market]: apay x [Bank]
Hello [Name],
I lead apay, a payments platform for digital platforms in Asia and the CIS. We operate a payment switch that gives marketplaces, messengers and SaaS companies one integration for cards, Apple Pay, Google Pay and local methods.
We do not hold a licence and are not looking to become a bank. We are looking for a partner in [market] whose acquiring [and virtual account] rails we can expose to our merchants through one integration. The bank keeps the regulated activity and settlement; apay brings the merchants, the technology and the integration work.
What a partnership looks like:
- apay builds and certifies a connector against [Bank]’s API (fixed scope, 2 to 4 weeks in sandbox)
- pilot with two platform merchants under capped volume, then routing rules send [Bank] the traffic it wants
- commercial model of your choice: referral plus technology fee, PayFac under the bank, or white label
You can see the product working today: https://apay.to/checkout (works on a phone) and the partner brief at https://apay.to/partners/bank-partner-overview.
Could we take 45 minutes in the next two weeks with you and one API owner? I will bring the integration requirements and our due-diligence pack in advance.
Best regards, [Name], apay [phone] · partners@apay.to
Bank partnership, follow-up (5 business days later)
Subject: Re: Platform payments partnership in [market]
Hello [Name], following up in case this went past. Two concrete things we can do in a first call: map [Bank]’s [API name] to our connector checklist live, and show a payment from a phone through the sandbox with webhooks arriving on the merchant side. If someone else owns fintech partnerships at [Bank], I would be grateful for a pointer.
Processor or BaaS intermediary
Subject: Connecting apay merchants to [Processor] in [market]
Hello [Name],
apay is a payments platform with an existing [Processor] connector. We are onboarding platform merchants in [market] and would like to route their volume to [Processor] under [a master account / individual merchant accounts].
Could you share the sandbox credentials and the onboarding requirements for a platform model, and who handles partner accounts? Product: https://apay.to, docs: https://apay.to/docs.
Pilot merchant
Subject: Payments for [Merchant]: cards, Apple Pay and Google Pay in one integration
Hello [Name],
We are apay, a payments platform for platforms in [market]. In one integration you get cards, Apple Pay, Google Pay and [local methods], a hosted checkout that runs on any phone, a dashboard and signed webhooks. There is no lock-in: the API is standard and portable.
We are selecting three pilot merchants for [market]. Pilot terms: no setup fee, [rate] for the pilot period, engineering support from us, and we handle processor onboarding.
Try it in two minutes on your phone: https://apay.to/checkout. Quickstart for your engineers: https://apay.to/docs/quickstart.
Would a 30-minute call this week work?
Warm introduction request
Subject: Intro to [Bank] fintech partnerships?
Hello [Name], we are talking to banks in [market] about sponsoring platform payments for apay (https://apay.to). If you know the digital partnerships lead at [Bank], a two-line intro would help a lot; I have a short brief you can forward: https://apay.to/partners/bank-partner-overview.
Sequence
| Day | Touch |
|---|---|
| 0 | First email with demo link and brief |
| 5 | Follow-up with one concrete offer for the call |
| 12 | LinkedIn message to the same person or a peer, or a warm intro request |
| 20 | Last email: “closing the loop”, ask whether to check back in a quarter |