Reported details
What happened
Shopify’s Payments Apps API accepts B2B payment session requests without family_name in shipping_address or billing_address.
The Payments Apps API request reference now documents family_name as optional for B2B orders.
The change affects payments apps that currently require shipping_address.family_name or billing_address.family_name for B2B checkouts.
This is a global platform update in the supplied event, based on a single official Shopify Developer Changelog record.
Business relevance
Why it matters
A payment app that rejects an absent surname could interrupt eligible B2B checkouts even though the platform accepts the request.
B2B address data may not include the same individual-name fields as consumer checkout data, so validation needs to reflect the order type.
The requirement is relaxed for B2B orders only; the supplied evidence does not extend this change to other checkout types.
Editorial perspective
Analysis & judgment
The practical issue is validation scope: an app should distinguish B2B requests before deciding whether family_name is required, rather than treating every address payload identically.
Apps that already accept missing family_name for B2B requests have no indicated implementation change, while apps with unconditional checks are the likely remediation target.
Because the evidence confirms acceptance and documentation alignment but provides no incident or performance data, merchants should treat this as a compatibility update rather than evidence of improved conversion.
Applicability
Seller impact
Merchants using a third-party payments app for B2B checkout may see no visible change if that app already handles missing surnames; otherwise, checkout failures are possible where the app enforces the field.
The direct implementation impact falls on payments-app developers, while merchants should confirm their provider supports B2B addresses with family_name absent.
This update does not indicate a change to shipping, billing, or fulfillment requirements beyond the Payments Apps API request validation described.
Action plan
What to do now
- 1
Review B2B address validation
nowIf your payments app requires shipping_address.family_name or billing_address.family_name, update the B2B validation path to accept requests where the field is absent.
- 2
Test both address shapes
this-weekRun a B2B payment-session test with family_name present and another with it missing in shipping and billing addresses, then verify the app continues its normal payment flow.
- 3
Check provider compatibility
monitorAsk your payments provider whether its implementation follows the updated Payments Apps API behavior, especially if your store depends on B2B checkout.
What not to do yet
- Do not remove family_name validation for every order type based on this update; the supplied evidence limits the change to B2B orders.
Sources & context
Evidence and sources
A source may provide only a headline or summary. Read the evidence scope below. Links and workflow checks are not independent fact verification. Internal confidence values are workflow signals, not probabilities of factual correctness.
- 01Source link
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 i
Shopify Developer Changelog · Workflow status: single-source
Retrieved: September 15, 2026 at 06:07 p.m. UTC
Claim is bounded to the ingested title or summary; no source body or quotation is retained.