Providing software applications that require a payment component with strategic payment gateway integrations. Provided expert testimony before the U.S. Congress on the risks around the processing of ACH credit transactions.It's common practice for a software development to choose a payment integration without having considered possible ramifications down the road, how it might assist the development's business model or best benefit the application's user base.A strategic payment integration should be a partnership between the application and the payment integration partner. Here are some points to consider:✓ Is there a potential need for multiple payment vehicles? Companies who accept both credit cards and checks will benefit their user base by integrating to a solution that provides both payment vehicles. * Some gateway integrations may offer both, but the pricing is likely to be higher than market on the e-check side.✓ Does the application serve Canadian users as well as USA? Few gateway integrations can provide a single platform that facilitates both USA ACH e-checks and Canadian EFT.✓ Data as a Hostage: It's commonplace for merchant account providers to hold the data hostage, almost literally. They might either have exorbitant fees associated with migrating the data or are not willing to facilitate the merchant's migration needs. Know your situation before it becomes an issue.✓ As a partner with your payment gateway provider, you and your application should be participating is a residual revenue share. This can be accomplished while still providing market or better than market rates.✓ Is payment aggregation a possibility for your application? Applications that know their client base may be in a position to become a payment aggregator, also known as PSP or Payfac. There are pro's and con's to understand, but for the right application, a Payfac model might be a great way to enhance the application and business.