#32069107 A4A: Enable referral cobranded checkout flag and refine logo options

Needs Translation

Created on March 5, 2026 , translate by Sunday, March 8, 2026 (in 2 days)

Translate 1 original (3 words) to Arabic Glossary

Prio	Original string	Translation	—
	Use this logo	You have to log in to add a translation.	Details
Use this logo Use this logo You have to log in to edit this translation. or Cancel Translation Memory Loading… Meta Status: untranslated Priority: normal More links: Permalink to this original All translations of this original Show all translations across locales Show original across locales Show all deliverables with this original (ar) Show all deliverables with this original (overview) View deliverable: A4A: Enable referral cobranded checkout flag and refine logo options

Legend:

Current

Waiting

Fuzzy

Old

With warnings

Export strings as

Enable the a4a-referral-cobranded-checkout feature flag for A4A stage and production environments.
Refine the referral logo radio options so the second option label is dynamic:
- “Use a different logo for this referral” when a profile logo exists.
- “Use this logo” when only an agency referrals logo exists.
- “Upload my logo” when no logo exists yet.

Roll out the cobranded referral checkout experience beyond dev/horizon so agencies can use the same flow in stage and production.
Make the referral logo choices clearer and more contextual, especially when an existing logo is already configured.

In the stage environment, verify that the cobranded referral checkout flow is available when requesting client payment.
In the production environment, verify that the cobranded referral checkout flow is available when requesting client payment.
With different logo states (profile logo only, referrals logo only, no logo), verify that the referral logo radio labels match the expected copy.

Has the general commit checklist been followed? (PCYsg-hS-p2)
Have you written new tests for your changes?
Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
Have you checked for TypeScript, React or other console errors?
Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
Have we added the “[Status] String Freeze” label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
- For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
For changes affecting Jetpack: Have we added the “[Status] Needs Privacy Updates” label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

Unfortunately, no screenshots were provided by the developer.