Cyberbacker Routed Encrypted Payment Files From PaySimple to Authorize.NET Without Custom Code

Cyberbacker is a virtual-assistant and back-office staffing provider headquartered in Ogden, Utah. Its roughly 1,500 employees work in distributed remote teams that handle administrative, marketing, sales, and back-office work for business owners and executives.

The payment-file transition ran through Cyberbacker’s affiliated brand, Moneybacker. Payment gateways held the settlement files and transaction batches recording what had been processed. So when Cyberbacker moved its payment processing from PaySimple to Authorize.NET, the switch was not just a matter of pointing new charges at a new processor. The payment data itself had to move.

Two Payment Gateways With No Path Between Them

It could not move directly. Authorize.NET would not accept a file directly from PaySimple. The two gateways had no interchange between them, and neither offered a way to hand payment files to the other. The data Cyberbacker needed on the new platform was stranded on the old one.

The cost of that gap was measured in third-party response and processing time. Each gateway operated on its own schedule, and Cyberbacker could not accelerate either side. Whatever sat between them would also be holding payment data in transit, which meant the files had to stay encrypted on every leg. There was no acceptable version of this where settlement files waited somewhere unprotected.

Neither Endpoint Was Theirs to Change

What made the problem stubborn was that Cyberbacker controlled neither end of it. Both systems belonged to payment processors with their own formats and schedules, and none of that could be modified from outside.

That ruled out the obvious answers. Cyberbacker could not ask either gateway to build a path to the other. Handling encrypted payment files by hand was not defensible. And commissioning a custom integration between two third-party systems meant building and maintaining software for a bounded transition, while the technical work on Cyberbacker’s side was carried by an outside fractional technology leader.

What the fix had to do was clear before any product entered the picture: sit between two systems Cyberbacker did not own, speak the SFTP both gateways could use, keep each gateway’s access separate from the other’s, decrypt and re-encrypt files automatically on each leg, and move files between the two sides without a person in the loop or a line of custom code. Cyberbacker selected Files.com to be that landing zone.

Two Gateway Credentials, Two Folders, One Automation

The build was small and deliberate. On a single Files.com site, Cyberbacker’s fractional technologist set up a dedicated SFTP credential for each gateway, each scoped to its own integration folder. PaySimple delivered into its side; Authorize.NET collected from its own. Neither gateway could see the other, and neither had to change how it connected because SFTP was already a path both could use.

Encryption became folder configuration instead of a manual step. Using Files.com’s per-folder PGP handling, files landing from the outbound gateway were decrypted automatically on arrival, and files staged for the receiving gateway were re-encrypted automatically before pickup. The data traveled protected on both legs without anyone running a key or a script by hand. Between the two folders, a Files.com Automation did the routing: each file that landed on the PaySimple side was copied to the Authorize.NET side on its own.

All of it was configured, not coded. Nothing was installed at either gateway, and no integration software was written.

The Missing Path Was No Longer Cyberbacker’s Problem

With the route live, a transfer the two payment processors could not perform between themselves became a defined, encrypted, automated hop through Files.com. Each file was decrypted, routed, and re-encrypted without a person handling it, while folder configuration enforced encryption on both legs.

Cyberbacker’s sequencing still depended on the gateways’ own response and processing schedules. But the person coordinating the transition now worked against those clocks—the only clocks left—without also managing manual encrypted-file handoffs or maintaining a one-off integration.

Neither gateway changed anything to make that true. Each connected to Files.com over SFTP, and Files.com did the rest. Two systems with no direct path between them did not need a custom bridge built into either one. They needed a governed place in the middle, and Files.com was that place.