Swap one URL. Protect the traffic behind it.
Put the proxy in front of an API or a vendor. Rules name the fields to tokenize on the way out and to restore on the way back, across JSON, forms, XML and SOAP, multipart uploads and headers.
Older bank and verification APIs, and vendors you can't change, still need to work. Rewriting every integration before a deadline isn't realistic.
Add a route
Point a route at the upstream service and swap its URL in your app.
Write field rules
Name fields such as $.customer.bvn, or let detection find what you missed.
Traffic flows
Whatever the proxy cannot read in full, it does not forward.
Same request, different host
# Before: https://api.kyc-vendor.example/v2/verify
curl https://proxy.onshore.ng/$ROUTE_ID/v2/verify \
-H "X-RV-Route-Key: $ROUTE_KEY" \
-H "Content-Type: application/json" \
-d '{"customer":{"bvn":"22123456789"}}'
# The vendor receives: {"customer":{"bvn":"tok_bvn_7Hq2xP9LmA4c"}}JSON, forms, XML, SOAP
SOAP envelopes arrive intact, with namespaces and order as they were sent.
Multipart and files
Fields and text files are read. Binary parts follow a file policy.
Headers both ways
Protect values in headers, and detect them in query strings.
Reads the bytes
What the content actually is decides how it is handled, not the label on it.
Inbound and outbound
Protect traffic coming to you and traffic leaving for vendors.
Refuses what it can't read
It fails closed instead of guessing.
Start with one leak.
Tell us which flow worries you most. We'll show you what it would take to keep it onshore.