About Us
What We Do
Fundraising Maica AnimalOS Non Profit Payments AI
All offerings
Impact Stories
Let's talk
Payments

Payments that land where they belong.

Gateways integrated directly into Salesforce, so money coming in becomes a record, a receipt and a reconciled line without anyone retyping it.

A payment is not an event. It is a record.

Most gateways are very good at moving money and completely indifferent to what happens next. The gap between the two is where the manual work lives.

No export, no re-keying

The gateway writes straight into Salesforce. Nobody downloads a settlement file on Monday and types it into the system that was supposed to replace typing.

The failed ones matter most

Expired cards quietly end regular giving. Retries, reminders and recovery handled automatically save more income than any campaign you could run instead.

Card data you never hold

Numbers are tokenised at the gateway and never touch your environment, which keeps PCI scope small and keeps the awkward question off your risk register.

Seamless integration

Straight into Salesforce.

  • The gateway talks directly to your Salesforce org, so a payment becomes a record the moment it clears.
  • No nightly file, no manual import, no window where the two systems disagree with each other.
  • Receipts, thank you journeys and allocations trigger from the payment itself rather than from somebody remembering.
Salesforce Payment gatewayAuthorised and settled $40.00 $250.00 $75.00 $1,000 Record created Receipt issued Journey triggered
Every payment method

However people want to pay.

  • Cards, Apple Pay, Google Pay, direct debit, BPAY and PayTo, all landing in the same place.
  • Offline gifts, cheques and bank transfers recorded against the same record, so the total is the real total.
  • Fewer abandoned payments, because the option people expect is already there on the page.
All in one placeOne supporter record Cards Apple Pay Google Pay Direct debit BPAY PayTo Cheques, cash and bank transfers
Recurring and retries

Stop the quiet leak.

  • Most regular giving is not cancelled, it fails. An expired card, a declined transaction, and nobody notices for a quarter.
  • Automatic retries on a sensible schedule, card expiry reminders sent before the failure, and a clear view of what recovered.
  • Donors update their own details rather than ringing the office, which is usually where the relationship ends.
Monthly gift, $40Alex Nguyen Payment declinedCard expired, 3 May Reminder sent to the donorUpdate your card, one link, no phone call Retry scheduledAttempt two, three days later Payment recoveredGift continues, donor never rang the office Recovered this month$4,320
Reconciliation

Finance stops chasing.

  • Settlements, fees and refunds matched against transactions automatically, with the exceptions surfaced rather than hunted.
  • One month end process instead of three systems that each disagree by a few hundred dollars.
  • Reporting that the board, the auditor and the fundraising team can all read from the same source.
GATEWAY Settlement 4471$4,212.60Settlement 4472$1,988.00Refund batch 118-$240.00 SALESFORCE 118 gifts$4,212.6054 gifts$1,988.003 refunds-$240.00 Month end reconciledNo exceptions outstanding
Security and compliance

Card data you never hold.

  • Card details are tokenised by the gateway. Your Salesforce org stores a token, never the number, which keeps your PCI scope small.
  • Hosted payment fields and strong customer authentication handled by the gateway rather than built by us.
  • Access, audit trails and data residency configured deliberately, because in your sectors that is the first question procurement asks.
Card number 4242 8891 3307 1194 •••• •••• •••• 1194 Expiry08 / 29 CVC••• Stored in Salesforcetok_1QZa4xK2mN8pR7vB PCI scope kept small You never hold the number

Talk to us about payments.

If finance and fundraising are reconciling from different numbers, that is usually a gateway problem rather than a people problem. Worth a look.

Say Hello
Copyright Vertic 2026