JDeen

arrow_back Back to Services
Payments Infrastructure

Switch Payment Gateways Without Losing Saved Cards

Card and bank details tokenized with Evervault or VGS, so they belong to you and not your gateway, plus 3-D Secure with 3dsecure.io, Ravelin or Paay.

Discuss Your Project arrow_forward View Work History
A monitor showing a card vault that swaps a masked card number for a token and routes it to Gateway A or Gateway B, a blank card on the desk beside it
A laptop showing stored customers with masked cards and token IDs, and a switch moving payments from Processor A to Processor B
A phone on a stand showing a 3-D Secure screen asking to confirm a purchase with a passcode and a Verify button, a blank card behind it
In payment gateways
10 years
Gifts a year at GivingFire
$100M+
Gateways built
2
Shipped at Edge
3DS + 3RI

Your Customers' Cards Should Belong to You

When your gateway stores your customers' cards, it holds your recurring revenue. Moving to a cheaper or better processor means asking every customer to enter their card again, and many never do.

A third-party vault such as Evervault or VGS keeps card and bank details outside your gateway and out of most of your PCI scope. Your application stores only tokens, and the vault forwards the real details to whichever processor you choose, so you can route, fail over or switch without losing a single saved card.

Tokenization PCI DSS 3-D Secure Gateway Migration
lock

Vault Integration

Card and bank account collection with Evervault or VGS, through hosted fields and secure proxies, so raw numbers never touch your servers.

alt_route

Multi-Gateway Routing

Send tokenized payments to any processor, route by cost or card type, and fail over when a gateway goes down.

verified_user

3-D Secure

3DS2 authentication with 3dsecure.io, Ravelin or Paay: frictionless flows, challenges, and 3RI for merchant-initiated payments.

shield_locked

Card Migrations and PCI Scope

Stored cards moved out of your current gateway into a vault you control, and your PCI DSS scope kept as small as it can be.

Track Record

10 Years Inside Payment Gateways

Since 2017 my work has been payment infrastructure: first as the sole engineer on GivingFire's gateway, then building and leading engineering at Edge Payments Technologies. Systems that move money leave no room for shortcuts, and I bring that standard to every project.

payments

Edge Payments Technologies

Lead Software Engineer and Head of Compliance · 2022 – present

  • check_circle Built the Rails payment gateway, integrating the RS2, NMI and Moov processors for card and ACH.
  • check_circle Implemented 3-D Secure (3DS and 3RI) authentication for card payments.
  • check_circle As head of compliance, turned sponsor bank and card network requirements into controls built into the platform.
volunteer_activism

GivingFire

Senior Software Engineer · 2017 – 2022

  • check_circle Sole engineer on a payment gateway processing $100M+ in gifts a year across card, ACH and cash.
  • check_circle Built a custom subscription billing engine, where every saved card is recurring revenue.
  • check_circle Served about 250 churches and non-profit organizations.
See the full work history arrow_forward
Providers

Vaults and 3-D Secure I Work With

lock Tokenization vaults

Evervault
Encrypts card and bank data before it reaches your servers, and its relay decrypts it only on the way to your processor.
VGS (Very Good Security)
Collect forms plus inbound and outbound proxies that swap aliases for real card and bank details in flight.

verified_user 3-D Secure providers

3dsecure.io
A standalone 3DS server, so you authenticate a card once and charge it with any processor.
Ravelin
3DS authentication alongside fraud scoring, so challenges go to the payments that need them.
Paay
A gateway-independent 3DS2 authentication service.
The Delivery Path

How We Get There

query_stats

Audit

Where your cards are stored today, your gateways and your PCI scope.

lock

Vault

New cards collected through Evervault or VGS, with only tokens stored.

swap_horiz

Migrate

Saved cards exported from your gateway into the vault, PCI-compliantly.

alt_route

Route

Payments sent to any processor, with no customer re-entering a card.

Transparent Pricing

Scope-Based Engagement

  • check_circle Discovery & Requirements Session
  • check_circle Technical Architecture Document
  • check_circle Source Code & Documentation Handover

Project Pricing

Custom Quote

Scope-based pricing tailored to your project complexity and timeline.

Hourly Rates

Short-term contracts

$50/hr

Advisory, code review, fixes, and short projects.

Long-term, full-time

$30/hr

Ongoing full-time contracts, working as part of your team.

Common Questions

Will my customers have to enter their cards again? expand_more

Usually not. Most gateways will export stored cards to another PCI-compliant party on request. Once the cards are in your vault, every later gateway change is a configuration change, not a migration.

Does a vault remove the need for PCI DSS compliance? expand_more

No, but it shrinks your scope, often to one of the shorter self-assessment questionnaires, because raw card numbers never reach your servers. I help you document what remains.

Do I need 3-D Secure? expand_more

In the UK and EU, Strong Customer Authentication requires it for most online card payments. Elsewhere it shifts liability for fraudulent chargebacks to the card issuer and can raise approval rates. A standalone 3DS provider lets you authenticate once and charge with any gateway.

Want to Own Your Customers' Card Data?

Tell me about your gateways, how you store cards today and where you want to be, and I'll get back to you with a plan.

View Work History