There’s nothing like a summer evening baseball game: the smell of popcorn, the fun of eating Cracker Jack and the thrill of cheering for your favorite team. At InstaMed, we have a few teams we root root root for – the Philadelphia office cheers for the Phillies and in our Newport Beach office, their home team is the Los Angeles Dodgers. As for me, I support the Milwaukee Brewers. In light of the summer baseball season, I decided to put together a home run guide for integrating payments into your web application or portal. InstaMed’s Developer Portal is filled with easy ways to integrate payments into your workflow seamlessly and securely. You’ll see all the ways that InstaMed’s solutions dramatically reduce your PCI compliance efforts including achieving an SAQ A.
Here’s your home run guide to easily integrate payments into your web application or portal to reduce your PCI compliance efforts while increasing security at your organization this summer:
First Base: Secure Token
The InstaMed Secure Token allows you to accept eCommerce payments directly within your existing consumer application while being eligible for an SAQ A. Secure Token enables healthcare organizations to deliver a seamless and secure online consumer payment experience within their existing portal while preventing sensitive cardholder data from touching their servers. A few of the benefits of using the InstaMed Secure Token include:
- Highest Reduction in PCI Scope: When the InstaMed Secure Token is implemented, organizations reduce PCI scope to the SAQ A, which significantly reduces the risk of a data breach and the ongoing efforts of PCI compliance.
- Superior Consumer Payment Experience: Enable consumers to quickly pay and securely store payment methods in a digital wallet for easy future payments, from directly within your existing portal.
- Increased Efficiency: All payments are posted in real time.
- Easy to Integrate: No code changes are required for existing portals integrated with InstaMed Connect.
Learn more about the full InstaMed Secure Token process flow.
Second Base: iFrame
InstaMed user interface screens can be displayed in several different modes to match both application and user needs. These interface screens keep sensitive data off your healthcare servers and deliver a positive experience for your users. Learn more about how iFrame interfaces can be used.
7th Inning Stretch: Tokenization
Tokenization increases security at your organization by securely storing card or bank account information for future payments. It gives consumers the ability to save payment methods on file in a digital wallet. This is very similar to a buying experience on Amazon where consumers can choose the payment method that works best for them. Plus with tokenization, the actual cardholder data is stored by InstaMed and not by your organization, which keeps payment information off your server. Tokenization eliminates the need to re-enter credit card information into a system, reducing PCI compliance efforts and ensuring data is secure. InstaMed enables omnichannel payment tokenization which allows payment methods to be shared with consumer-facing and staff-facing applications. It makes for a convenient experience for both consumers and staff, all while increasing security at your organization. Learn more about the benefits of tokenization.
Third Base: In-App Apple Pay®
Apple Pay is a mobile payment and digital wallet service by Apple Inc. that allows iOS users to make payments using their compatible mobile device. In-app Apple Pay leverages both public key encryption and tokenization to secure the cardholder’s payment card data. This results in a significant reduction in the number of applicable PCI controls while allowing vendors to maintain the user interface. Plus, post-back of the payments is done in a real-time, web service call. InstaMed offers a full description of the in-app flow of Apple Pay along with sample code your organization can use to implement Apple Pay for payments. Learn more about in-app Apple Pay.
Home Plate! SSO with SAML or NVP
Single sign-on (SSO) enables users to pass seamlessly from a provider’s application into the InstaMed environment. SAML or NVP authentication via SSO is used to create and build a consumer experience over multiple visits. With SSO, you can enable advanced features like a digital wallet, self-service payment plans, eStatement authentication, text messaging enrollment and the ability to view balances. Plus, users don’t need to log in or sign up for a separate account to allow payment history, payment plans or consumer statements to be populated in InstaMed solutions. Your application can link directly to InstaMed screens like “New Payment Plan” or “View Payment History.” Learn more about the full integration options of SSO with SAML or NVP.
Don’t strike out this summer when it comes to security. Protect your organization by easily integrating payments into your web application or portal. By doing this, you can reduce your PCI compliance efforts including achieving an SAQ A, all while bringing home the game-winning run.