Payments engineering at RedNote

Backend engineering on the payments team of RedNote, a Chinese social media and shopping app: six pieces of work on the Java microservices behind checkout, security, currency exchange, refunds and risk control.

Backend engineering intern, Payments·May – Aug 2026·Shanghai, China

Diagram of the areas of payments work at RedNote: checkout, a security fix, PayPal transaction summaries, refund routing, risk data and support tooling.

01Checkout

Deciding which payment methods the checkout shows

A lookup that runs before checkout and returns which payment methods to offer, built across three microservices with an internal RPC call and an HTTP endpoint. The rules account for the device, app and browser, and operations staff can switch a payment method off and show a notice through configuration (Apollo), without a code release.

I also wrote emergency runbooks so operations staff can handle common failures without engineers.

02Security fix

Responding to a critical vulnerability in a shared Java library

In July 2026 a remote-code-execution flaw was disclosed in a widely used Java library for reading JSON, with no patch coming. I audited the payment codebase's dependencies to separate our own use of the library from use inside shared internal libraries, and flagged what each owning team needed to fix.

I then led the fix in the core payment services: moving them to a different JSON library, and turning on the library's safe mode wherever it couldn't be removed yet.

03PayPal

Bringing in PayPal transaction summaries for currency exchange and reconciliation

Automated the daily intake of the company's own transaction summaries from its PayPal account, which feed currency exchange and finance reconciliation. I built it on the existing file-download framework rather than adding a new scheduler, mapped the records to internal types, and rolled it out gradually.

04Refunds

Choosing which bank accounts refunds are paid from

Funds held at different banks earn different interest, so where outgoing refunds are drawn from matters. I added a configurable routing rule for this, split between a service that decides the route and one that keeps the counts, and reorganised the routing settings into an ordered list with gradual-rollout options so new rules can be added and switched on step by step.

05WeChat Pay

Sending risk data to WeChat Pay

WeChat Pay asks platforms to send extra details with some payments for its fraud and risk checks. I mapped its specification against the existing payment flow and carried the required fields from order creation through to payment across two services.

06In-app purchases

A self-service lookup for users' Apple in-app purchase records

Support staff had no way to look up users' Apple in-app purchase records directly in the internal portal. I built, on my own, a lookup tab there so they can check a record themselves: a Java endpoint that reuses an existing internal service call, and a table showing what they need.

07Stack

  • Java
  • Spring Boot
  • Microservices
  • Thrift RPC
  • Apollo config