In this article

A payment systems company's identity often accompanies another business's selling environment. A shopper may see the store prominently and encounter the platform in a much smaller area. The commission should explain the platform's role without confusing the two identities. Supply existing merchant-dashboard, customer-screen and any device examples. A large dashboard heading and a narrow shared signature create different acceptance needs. Commissioning the identity should not automatically be treated as commissioning the entire payment interface or its implementation.

Quick answer

Separate the platform identity from merchant and partner signatures in a payment systems logo commission. Test merchant dashboards, customer payment headings and any terminal application. Show how small-use artwork connects to the full name. Deliver screen and physical assets separately, using client-approved specialist content rather than deriving security, transaction-success or service-condition claims from the explanation of the logo.

Define two different audiences in the brief

The relationship with a merchant can differ from the encounter with a shopper. Mark the intended audience on each supplied screen. The platform name may lead a merchant dashboard while the shop leads a customer page. The designer should not establish that hierarchy independently; product and content owners explain the approved relationship. This prevents the commission from being shaped only around the company's own promotional website.

Populate the shared payment heading

Request a heading containing a long shop name, platform identity and other existing marks. Do not remove real information merely to make the new signature more visible. Prepare a second specimen with a short merchant name. The shared arrangement can be delivered as a separate template without merging the shop identity into the platform master. Review concerns naming relationships around an approved screen rather than technically redesigning transaction flows.

Explain the name and symbol in restricted space

List uses containing a single-line name separately from uses containing only a small symbol. If the new shape appears without the name, discuss how its connection to the platform is introduced elsewhere. Examine actual screen dimensions; a large presentation image should not settle small-use acceptance. Icon outputs, dashboard headings and shared signatures may require different forms, with the digital team supplying those needs at commissioning stage.

Review any terminal application separately

When device artwork is requested, supply the existing surface with its manufacturer identity and approved information areas. Test the platform signature within those boundaries. A representative photograph, measured artwork and physical manufacture are distinct deliveries. Do not turn identity design into a decision about device functionality. The terminal supplier may need different formats from the screen team, so the scope should identify both sets of requirements independently.

Rehearse another merchant relationship

A hypothetical platform works with a store whose own identity is visually dominant. Compare that arrangement with another merchant carrying a much longer name. Test whether the platform remains identifiable without creating another master logo for each customer. Statements about security or service characteristics remain client-approved wording. The scenario claims no transaction outcome; it is a visual acceptance exercise examining identity hierarchy across different merchants.

Deliver a usable set to the product team

Name master vectors, small-use artwork, dashboard headings and partner templates separately. Identify which screen examples are acceptance presentations and which are implementation assets. The team adding another merchant should test editable fields in a specimen. Keep unrelated supplier signatures outside the corporate source artwork. Record who adapts another product or device model and which accepted applications need review when those new surfaces are introduced.

Key takeaways

  • Explain merchant-facing and shopper-facing identity priorities separately.
  • Review a populated checkout heading with a long shop name at real size.
  • Distinguish interface specimens, device visuals and working-product delivery.

Frequently asked questions

Should the platform identity lead the merchant's?

The approved product communication relationship determines that. Keep both roles understandable rather than selecting an arrangement solely because it gives the platform more space.

Can a check symbol become part of the identity?

Review whether it could be confused with transaction status or independent assurance on the actual screen. Do not justify the new identity as an expression of transaction approval or a security claim.

Does the commission complete the checkout page?

It covers only defined visual tasks. The full interface, functionality and technical implementation may be separate projects; distinguish representative screens from a working product in the proposal.