family_name is optional for B2B orders in Payments Apps API requests

B2B checkout treats the buyer’s surname as optional, so payment session requests for B2B orders can omit family_name in shipping_address and billing_address. This affects payments apps that handle B2B orders through the Payments Apps API and currently require family_name in these addresses.

What changed

B2B checkout doesn’t require a buyer surname, and the Payments Apps API already accepts payment session requests for B2B orders without family_name in the shipping_address or billing_address. The Payments app request reference now documents family_name as optional for B2B orders to match this behavior.

Who's affected

Payments apps that use the Payments Apps API to process B2B checkouts and validate that shipping_address.family_name or billing_address.family_name is always present are affected. Payments apps that already accept requests without family_name for B2B orders don’t need to change anything.

What to do

If your app currently requires family_name in the shipping_address or billing_address for B2B orders, update your validation so it accepts payment session requests where that field is absent for B2B checkouts. Confirm that your app still behaves as expected when family_name is present or missing in these addresses.

Related docs

• Payments app request reference