Skip navigation
All Places > News > Blog > Author: andrew.harris

News

5 Posts authored by: andrew.harris

If you're a developer looking for Worldpay test cards for point of sale testing, you need to know how to obtain information about the appropriate integration processes, interfaces, and workflows.

 

This article covers the procedures for finding the appropriate support from Worldpay's Business Development team that you will need to acquire physical cards or e-commerce card numbers for performing test transactions.

 

Following the correct workflow is essential when starting a Worldpay payment implementation, and — as part of that— requesting test cards or test card numbers.

 

This process ensures we can give you the required information and support so that your application works as intended.

 

Integration for New ISVs

The Worldpay One Network Experience is a developer network for payment professionals. It is a comprehensive and accessible developer program that makes it easier to integrate payments into any application. You can find all the tools and resources you need in one place at the Worldpay ONE portal.

 

If you are a new vendor, start by initiating a conversation with Business Development and working with one of our Developer Integration (DI) consultants. Start by submitting the Worldpay partner contact form. The Business Development team will guide you through the rest of the process.

 

Integration for Existing ISVs

If your organization is already a Worldpay vendor, it's still best to get in touch with your Business Development contact, hold a kickoff meeting, and discuss requirements.

 

Even if you're working exclusively with card-not-present transactions (e-commerce), you still need to go through the Business Development and kickoff meeting process.

 

Worldpay's Business Development team will help you create long-term value for your organization, based on your market, customers, and relationships. The Business Development team works to understand how forces and variables within your business interact to create opportunities for your business’s growth. Worldpay's Business Development team will be focused not only on helping you grow revenues but also on understanding your market and helping you find the best payment solutions.

 

Express Interface Certification

The Express Certification Interface includes a set of requirements that an integrator must meet to obtain a certification for transaction workflows. These transactions may be card-present (such as retail), and card-not-present (as in direct marketing and e-commerce).

 

Documentation is available on Worldpay ONE, and the Developer Integration team (certification@vantiv.com) will provide the necessary information to allow you to complete the certification process:

  • Set up a Test Account to sign up for a free production-simulated test account to use during the integration process. This sign-up will grant you access to the API so that you can connect your solution to the Express Processing Interface.
  • Test Your Integration. The Worldpay Integrated Payments certification environment allows you to code, test, and evaluate your integration into the Express Interface, simulating a production environment.
  • Complete and submit the Request for Certification (R.F.C.) and Scenarios Document. This provides the Certification team with details about your software or hardware. If needed, Worldpay Integrated Payments will provide any additional certification documentation, test scripts, receipt requirements, and test cards.
  • Certification Testing and Review. In this phase, the integration team will provide you with all the necessary testing scripts. The team will also review test transactions and requests, advising you on any recommended changes to your integration and application.
  • Express Certification Letter. After you complete all requirements, you will receive an official certification detailing which functionalities implemented in your solution have been approved for use on the Express Interface.

 

Hosted Payments

The Hosted Payments solution supports three different processing flows:

 

  • Single Sale Transaction Flow
  • Single Sale Transaction with Embedded Browser Control Flow
  • Store Card Data in PASS to Tokenize Flow

 

A typical transaction using the Single Sale Transaction Flow will follow these steps:
 

  • Your app submits the sale data to Worldpay's Express Interface.
  • Express returns a transaction GUID if the request was successful.
  • Your app performs a redirect (full, popup, or iFrame) to Worldpay's Hosted Payments URL and appends the Transaction Setup ID to the end of that URL.
  • The end-user inputs the card into the Hosted Payments page/popup and clicks Submit.
  • Express redirects the details to the return URL you initially provided.
  • Your app receives the URL and parses out the response details.

 

The Single Sale Transaction with Embedded Browser Control Flow is similar to the Single Sale Transaction Flow but allows hosting the user interface in an embedded browser control.

 

The Store Card Data Flow is similar to the Single Sale Transaction Flow, but instead of sending a card number, your app stores the Payment Account ID token provided by Express and subsequently submits the sale using this token.

 

Card Issuance for the EMV Standard

EMV is a specification standard for smart card payments that was created in collaboration with leading card brands. EMV has replaced earlier information storage based on magnetic stripes, with the goal to standardize the "conversation" between cards and payment terminals.

 

Worldpay IP provides you with several tools to assist you during your coding, testing, and review phases. These include robust testing platforms, merchant IDs, test cards, and reports that let you review your transactions and results.

 

Your consultant will provide you with a set of EMV and magnetic stripe test cards along with a detailed, personalized test plan. Our test plans contain test cases that cover all of the transactions you plan to support. Our test plans are great learning tools for fine-tuning your payments knowledge and Worldpay-specific integration methods.

 

The MercuryPay Payments Platform

MercuryPay is Worldpay's award-winning platform for fast, reliable, and secure payment processing. You can rely on MercuryPay’s state-of-the-art processing engine — It meets the highest industry standards for security, robustness, and card brand compliance.

 

If your company is a member of the MercuryPay platform, arrangements will be made for Integration Planning, which includes a few steps.

 

Your company will be assigned a MercuryPay Developer Implementations Consultant during the integration with Worldpay IP. First, Worldpay IP will arrange a kickoff call with your team, which includes:

 

  • Deciding which features and functionalities you wish to implement.
  • Understanding the specific requirements for your target business.
  • Deciding which integration method best fits your POS architecture.
  • Reviewing MercuryPay integration specifications, data, and error handling.
  • Reviewing payment industry rules and regulations.

 

After the kickoff, you should do regular checks with your consultant to stay on track throughout the integration process.

 

Conclusion

Providing test cards for point-of-sale testing is just part of Worldpay's customer integration process.

 

Contacting Worldpay Business Development for proper guidance is key to a successful integration process, whether your company is a new ISV or an existing vendor starting a new integration.

 

You can contact the Developer Integrations Team by email integrationteam@vantiv.com

 

Useful Links

The links below provide additional in-depth information to guide you through a successful integration process:

 

Worldpay partner contact form

https://developer.vantiv.com/community/help-and-getting-started/main-contact-us

 

Express Certification Overview

https://developer.vantiv.com/docs/DOC-1450

 

Hosted Payments Overview

https://developer.vantiv.com/docs/DOC-1579

 

MercuryPay Platform Integration Guide

https://developer.vantiv.com/docs/DOC-1504

Who are the developers in our community? What got them into coding in the first place? How do they like to learn and troubleshoot? We asked 100 of our developer partners about their education, career path, coding preferences, and more. Here’s what we discovered.

 

Read the complete study.

Developers who code for payments are seasoned

45% of our developers have been coding professionally for a long, long time—over 10 years. Over 1 in 4 developers have been coding professionally for 5-10 years, and nearly 1 in 5 developers have been coding at work for 1 year or less.

 

Most began coding as kids

45% of the developers surveyed began coding before they were 17. 1 in 4 learned to code as young adults, from age 18-22.

As we kick off a new year, what does your payment roadmap look like? Are you looking to add a new feature to your payment stack or are you building out your PayFac strategy? Perhaps you are poised to begin your integration to Worldpay from FIS in North America. 

 

There is so much to consider when it comes to integrating payments into your point of sale [ Express API ] or hosted payments page. If you have questions about PCI Compliance or you are ready to talk to a payments professional we have the answers. If you want to learn more about integrated payments first, perhaps start here

 

Our solutions range from integrations for small businesses all the way to the enterprise.

Payment development can be daunting, and having someone to help you guide you through your journey is what Worldpay from FIS is all about. 

This community is geared towards North America Merchant Solutions, so if you are looking for eCommerce API documentation and are outside of the US, then check out our eCommerce API Portal

 

The payments landscape is ever-changing, integrations are becoming more layered, there are many value-added services that can be added; keeping up with complex data is now the norm. Worldpay from FIS have multiple solutions to keep you out-of-scope as well as experts to help you with Level II and Level III processing. 

 

So I ask you again, what does your 2020 look like in terms of adding or enhancing payments for your customers? Let us know, reach out to our team or add in a comment below. Happy New Year! Here's to an amazing year in payments! 

Learn how companies need to adapt to be competitive in this Payments Journal article and grab the most recent white paper from FIS on Consumer Preferences. 

 

Consumer Preferences Are Shifting. Here’s How to Keep Up. | PaymentsJournal 

when you are at a party - and no one wants to talk payments meme
 
In your mind what would be the outcome if a crowd of 500 payment geeks spread out in a large banquet room in Vegas for 36 hours? Do we truly understand the problems we are being asked to solve? Do we have visions of grandeur and want to pitch something revolutionary to get some coin? Or are we really anxious to see the actual APIs that the sponsors will be revealing that can be tied into our product for the ultimate win?
 
For the past five years; developers, designers, and entrepreneurs flock to Vegas late October to mingle with their peers and accept a themed challenge relating to payments and FinTech. This is Money2020 Hackathon.
 
Some are serial hackers that make the circuit, eager to win so they can pay for a future tank of gas to get them to a future hackathon. Some are students looking to test their skills and get real-world experience and rub elbows with key industry players. While others just want to get away and spend a nice sobering weekend freaking out and stressing over what the hell to do to make payments rad. Can you guess which category our team fit?
 
I won’t bore you with what Money2020 is, you can look it up. I won’t drone on about what a hackathon is either, you can figure that out too. What I will talk to you about is what we learned and in turn ask you to give feedback on innovation and FinTech in the comments below.
 
The Story 
It was a warm Colorado afternoon in early October when a group came together over a working lunch to put aside the day-to-day talk of payment-processing, back-office application sprint planning, and the usual dev chatter around all things relating to individual technical work as a payment geek and engineer. It was time to secure our war-room, erase the spaghetti and database diagrams from the whiteboard, and get a jump start on collectively ideating for the annual pilgrimage to the Money2020 hackathon.
 
"For good ideas and true innovation, you need human interaction, conflict, argument, debate."   - Margaret Heffernan
 
Have you ever tried to loosen a machine bolt and find that you just can’t get enough leverage to break free? This is generally the way our annual ideation meetings begin. At home I have penetrating oil that I can spray the bolt head with, wait a few minutes and generally it will loosen up. After 5 years, we still don’t know what our favorite penetrating oil is, but after a couple of lunch-time meetings we somehow manage to get that rusted bolt loose and can start ideating.
 
Our team is very intelligent and capable of implementing and designing just about anything, and now that we had our idea we needed to determine our technology stack. Do we go-for-broke and attempt to learn something new or do we stick to our wheelhouse and forgo any language-centric or environmental gotchas. Knowing that there would still be gotchas. There are always gotchas. 
 
So after some debate, the team decided to stick with what we knew best and start building out a test environment. The goal was to make sure when we access those infamous APIs come game day, we could easily hook into them and get the information we needed back to help drive our solution. 
 
“There’s a way to do it better—find it.”   - Thomas Edison
 
Our idea was still evolving, but the basic foundation was in place, and we knew what we were going to build it in. The next step? Well given that we all have families and lives outside of work; plus the fact that we only had a handful of working lunches to ideate and test environments the next step was - to board the plane of course. 
 
After landing in Vegas we headed over to the meet and greet, had a few appetizers, Goose Island IPAs, and chatted with the four sponsors. Our idea still held up when pitching to peers and sponsors alike at the party, so we headed to our rooms to prep a little bit and get a good nights sleep before coding was to begin around 11am the next morning. 
 
"Ideas are like rabbits. You get a couple and learn how to handle them, and pretty soon you have a dozen.”   - John Steinbeck
 
After very little sleep due to a wild party in the hotel room next door, the team met in the banquet hall the following morning and secured our table and checked in with the sponsors. Once the clock started we began our coding and we certainly ran into challenges and had to pivot some along the way. Many hours into the code we found that one of the original ideas that we glossed over in one of our "rusted-bolt" war-room meeting the week before came to surface and we decided to pivot and work on that idea alongside our original plan. 
 
Confident then that we could pitch to (2) sponsors, doubling our chances of failure. 
 
“I want to put a ding in the universe.”   - Steve Jobs
 
I love innovation and I love working with people I don’t get to everyday in order to learn and grow not just professionally but as a human as well. Each year there are new faces that go with us to the hackathon and it is such a great experience. My advice is to get out of your comfort zone on occasion, it really can do wonders. 
 
Code Or It Didn't Happen
 
So you notice I didn’t talk at all about our idea or what we pitched. I first wanted to give you inside access to the repo and see the code for yourself. We will do a followup article if there is interest, but until then let us know what you think and ask questions below in the comments or tell us perhaps about a payment or hackathon experience you have had in the past. Also, should Worldpay do a hackathon for you guys as payment developers? Could be virtual or would you like to all met in Denver and code to some of our Worldpay APIs? We would like to know your thoughts.

 
“99 percent of success is built on failure.”   - Charles Kettering
 
We didn’t get to pitch our idea on the main stage or win any foam-core board checks that would not have fit in the overhead bin anyways. What we did come away with some great new ideas and will be spending some working lunches over the next few months bringing them to life and hope to share with you sometimes soon.