OperationsUpdated 15 July 2026

How do I collect visa payments online?

Short answer

Collect visa payments through a payment gateway connected to your application form, so the applicant pays at submission rather than by bank transfer later. Stripe and PayPal cover most markets; regional gateways like Barclays ePDQ or Ryft suit UK and multi-currency operations. Charge government fee plus service fee as separate lines, and make sure the system supports partial refunds.

Payment at submission, not by transfer afterwards — chased invoices are the main source of stalled applications.
VisaCRM supports Stripe, PayPal, Barclays ePDQ and Ryft, in GBP, USD, EUR, TRY and AED.
Partial refunds are non-optional: the government fee is often non-refundable while your service fee may be.

Where in the process should payment happen?

At submission, inside the application form. The moment you separate paying from applying, you create a chase: an invoice emailed, a transfer that arrives in three days, a reference nobody included, a reconciliation someone does by hand. Every one of those steps is a place the application stalls.

Taking payment at the point of application also filters intent. Applicants who complete a form and pay are committed; applicants who will not pay were never going to submit documents either. Your open case list stops filling with things that will never happen.

This is the e-commerce half of visa software, and it is the half most case-management tools treat as an afterthought. A checkout that sells a visa like a product is a different thing from a CRM that can record a payment.

Which gateways and currencies should you use?

Stripe covers most markets and is the default for card payments. PayPal matters where clients expect it, which varies a lot by source market — in some corridors it is the difference between converting and not. Barclays ePDQ suits UK operations with an existing banking relationship. Ryft handles split payments and marketplace-style flows, which is relevant if you are paying partner commission out of the same transaction.

VisaCRM supports all four, with multi-currency in GBP, USD, EUR, TRY, and AED. Charging in the applicant's currency rather than making them do the conversion measurably helps completion, especially in price-sensitive corridors.

Structure the charge as separate lines: government fee at cost, service fee with your margin, add-ons like express processing on top. Bundling them into one number hides where your margin actually is and makes refunds messy. Visa consulting pricing strategy goes further on the pricing model itself.

What about refunds, commissions, and reconciliation?

Partial refunds are not optional. A refused application often means the government fee is gone while your service fee is arguable. A system that can only refund the full amount forces manual bank transfers and a spreadsheet, which is exactly what you were trying to leave.

Commission needs to come out automatically if travel agents or sub-agents send you applications. Calculating it by hand at month-end is where partner relationships go to die — how travel agencies earn commission on visas covers the model.

Reconciliation should be automatic. Every payment matched to a case, every invoice issued without anyone generating it. Note that gateway fees are charged by the provider on top of your software cost — factor them in via how much visa CRM software costs. And tie payment events into your notifications so a receipt goes out on its own: automatic status tracking covers the mechanism.