Tech Talks vol.34 – Integration Consultant

About Tech Talks

In this Tech Talks series, we will share with you the attitude and vibe of the PayPay Tech Team through the voices of the unique product members from around 50 countries!
In this installment, we spoke to two active members of the Product Integration Team serving as sub-leaders.

Tell us about the Product Integration Team’s operations and mission

Asai:
The Product Integration Team provides technical support for the introduction of products developed for merchants. Specifically, we handle various implementation methods such as ‍integrating PayPay payment‍s into online platforms like e-commerce sites, introducing PayPay as a mini app, incorporating the PayPay payment functionality into merchant apps, and implementing PaaS-based offline payments. We provide implementation support by communicating with users, merchants, business teams, and product teams to offer the best implementation practices for merchants.

Our mission is to provide easy and high-quality integration for our merchants’ developers, contribute to increasing merchants’ GMV through PayPay adoption, and offer the best UX to users through products that connect merchants and PayPay.
Since implementation depends on the merchants’ technical expertise, our challenges involve increasing the speed of implementation, receiving feedback to improve the product, and delving into strategies to enhance our merchants’ GMV.

Tsukada:
There are many merchants in the online payment market, and we cannot directly intervene for small and medium-sized companies. In this situation, I believe ‍our big challenge is figuring out how to guarantee the quality of implementation and create a system to effectively follow the PDCA cycle. This is important to help increase the GMV for merchants.

What project stood out the most to you?

Asai:
It was a project for introducing PayPay payments for a certain e-commerce mall. We utilized a new product called Smart Payment, which incorporates PayPay functionalities in the UI of merchants using JavaScript SDK, but we faced challenges in communicating with shareholders both within and outside the company.

As it was a new product, it was difficult to make our partners understand its benefits. We also had to align the demands of the sales teams and merchants, customizing products in a way which we usually don’t do based on merchants’ requests and user impact.

Tsukada:
What particularly left an impression on me was the recent PaaS introduction project with a convenience store chain. This was the third PaaS implementation, and ensuring high quality with limited knowledge was challenging. The rollout ended up being two weeks ahead of schedule, causing quite a chaotic situation due to the insufficient implementation capabilities of the merchant. Ultimately, with the help of PayPay developers, we worked tirelessly from morning to night to overcome the challenges. Having said that, the effort was worthwhile as the partner’s app entered App Store rankings, allowing me to recognize the societal impact of introducing PayPay’s payment services.

On the other hand, as a service provider, I also realized the need to reduce dependence on the partner’s technical expertise. I would like to develop more detailed guidelines and strengthen the review process to lower implementation barriers.

What was your career like before joining PayPay and what prompted you to come here?

Asai:
I started as a software engineer after graduating from university and was engaged in directing new infrastructure systems as a secondee. Afterward, I worked on maintaining and operating web systems and constructing them on-site at an infrastructure company. In my previous job, I was a backend developer for payment platforms. I joined PayPay because I found the PayPay app appealing and believed my experiences as a payment system engineer and directing at an operating company could be put to use.

Tsukada:
I’ve worked as an infrastructure engineer at an independent systems integrator, a startup web contractor, and a web service company. In my last company, a consulting firm, I worked as an IT consultant. I chose to become a consultant because I wanted to refine my skills in understanding business at a higher level and engaging in discussions as a businessperson, rather than solely pursuing one aspect of the business, like development.

My transition was spurred on by a recruitment email, although at the time I wasn’t considering a job change. During the pandemic, as online payments became more common, I found the idea of code payments entering the online market appealing. I thought my experience could be valuable in this initiative, which is why I decided to join the company.

What are the fun aspects of working as an Integration Consultant?

Asai:
First, being able to popularize PayPay through merchants. Seeing users’ positive comments on social media after PayPay getting adopted makes me genuinely happy.

Second, the ability to interact with many stakeholders. Communicating with merchants, the business teams, and the product teams, among others, has broadened my perspective.

Third, the release of numerous products for merchants and the ability to take on new challenges. Although it can be demanding, it’s also helped me grow.

Tsukada:
Since I am interested in pursuing a career path that involves strategic business planning, such as CIO or CTO, I appreciate the opportunity to use technical skills in a business context and engage with customers as it provides me with valuable experience. The job refines negotiation and strategic skills when balancing what the company wants to achieve and customers’ benefits.

There are instances where decision-makers from major companies are present during meetings, and discussions involve presenting PayPay’s viewpoint against their feedback. I can also gain valuable experiences by directly engaging with our CEO, Nakayama-san.

What is the vibe like in your team?

Asai:
Basically, one person is in charge of each project so we work individually, but we get along well. We have amicable conversation not only about work but also about each other’s hobbies and interests.

Tsukada:
Nevertheless, considering our role in coordinating stakeholders internally and externally, there is some mature composure within the team as well. Also, although there can be tough situations depending on the project, we tend to be fearless.

Asai:
Having said all that, we ensure that no one is left struggling alone, and we don’t criticize someone for making a wrong decision. When necessary, we all help each other as a team.

What do you want to try out next at PayPay?

Asai:
As a team, we want to become capable of being a consultant for merchant systems in addition to integrating PayPay products, working towards the mission of contributing to ‍the merchants’ GMV. As an individual, I want our team to be the springboard for promoting product improvement.

Tsukada:
I want to offer PayPay solutions overseas!

Finally, any words for job seekers?

Asai:
PayPay is a company that has 58 million users and is taking on many new challenges even as its social responsibility grows. Integration requires both quality and speed, and is challenging and highly rewarding. Although you will need a technical background, we believe that those who maintain their standpoint and work through to the end despite uncertainties will be successful.

Tsukada:
PayPay is still a startup and a growing company. If you want to enjoy your personal growth and PayPay’s growth by traversing across different cultures—business, sales, and product—within the company, you are most welcome here!

*The recruitment status is current at the time of the interview.