For Upstart’s White Label Platform team

Make complex financial workflows feel simple.

I’m Cameron Nickert, a Senior Software Engineer on Shopify’s Payments Platform. I led the rollout of a unified refund API and championed the workflow that gives merchants time to review risky orders before fulfillment.

Comic portrait of Cameron Nickert
Detroit Metropolitan Area

Upstart works with banks and credit unions to make borrowing simpler and more affordable. I’m drawn to the White Label team’s part in that effort, helping lenders onboard through shared capabilities while preserving what’s distinct about each borrower experience.

In payments, I’ve had to decide what should stay common across providers and what needs to vary by payment method or market. I’d like to bring that judgment to both sides of lender onboarding, from designing the workflow to making the next step clear for the person using it.

  • ShopifySenior Software EngineerPayments Platform · 2022–present
  • IndeedSoftware Engineer IIIdentity Platform · 2021–2022
  • FordSoftware Engineering Team LeadPayments & Web Experiences · 2018–2021

M.S., Software Engineering · University of Michigan–DearbornB.S., Computer Science · Central Michigan University

Where my experience fits

Configurable partner capabilities
I built the foundations for a common refund API and led the rollout to third-party payment providers. At Ford, I led delivery of an embeddable payment library for multiple web properties.
Reliable financial workflows
I championed Hold for Review and implemented changes across payment and order workflows. We reused established payment behavior to keep authorization, capture, and fulfillment aligned with less custom recovery logic.
Partner onboarding
I integrated Bizum’s eligibility requirements into Shopify’s existing merchant setup and traced how new information reached the readiness check. That exposed gaps in both the form and the timing of the check.
Self-service tools and workflow APIs
I led Ford’s payment troubleshooting portal across the backend and React UI. It gave support teams a way to investigate payment failures without direct access to logs or databases.
Production reliability
I resolved bottlenecks in Shopify checkout migration paths and took part in load validation for peak events. I work with Rails, SQL, and Kafka, and have built cloud applications with AWS Lambda and Google Cloud Run.
Product and engineering collaboration
For Shop Pay Installments, I helped frame whether to show prequalification before checkout and built a prototype to test the idea.

Senior Software Engineer

2024 - 2025

Unified Refund API

I built the foundations for one refund API across providers and led the staged rollout. A common path made error handling and retries consistent and gave future integrations a pattern to reuse.

  • Payments
  • Refunds
  • Platform
More details

Senior Software Engineer

2026

Hold for Review

I championed the workflow that lets merchants pause risky orders for review while routine payments keep moving. I implemented changes across payment and order handling and took part in live validation.

  • Payments
  • Risk
  • Fulfillment
More details

Senior Software Engineer

2026

MB WAY & Bizum

Shopify Payments introduced local options for shoppers in Portugal and Spain. I extended eligibility checks and integrated Bizum’s onboarding requirements into the merchant setup Shopify already used.

  • Payments
  • Onboarding
  • Platform
More details

Senior Software Engineer

2023 - 2024

Redesign Payments API for Third-Party Gift Card Support

A gift card and another payment method needed to work in one checkout even if they completed at different times. I built the orchestration foundations for that workflow.

  • Payments
  • Orchestration
  • Redeemables
More details

Software Engineering Team Lead

2019 - 2021

Ford Payment Library

I led delivery of an embeddable payment library that gave Ford web properties a shared integration for reservations and digital purchases.

  • Payments
  • SDK
  • Security
More details

How I work

Reuse what already works.

For Hold for Review, we realized the established payment flows already handled much of the lifecycle. That gave us fewer recovery paths to build, maintain, and test.

Start from the user’s next step.

In Bizum setup, I followed a missing requirement as a merchant would. That let me see the gap between a correct eligibility rule and a form that made it hard to act on.

Plan for the rollout in the design.

On refunds, I built for consistent retries and added monitoring and safeguards. I led the rollout in stages because verifying the migration was part of delivering the API.

Let’s talk about the next partner.

I’d love to hear which parts of onboarding repeat today, where lenders need room to do things differently, and what a better first launch would look like for them and their borrowers.