Custom branding for crypto invoices: logos, colors, PDFs, and hosted pages that build trust

Your client opens an invoice email. They click the payment link. What they see in the next three seconds determines whether they pay immediately or pause to Google your company name. Crypto checkout already asks for more trust than card checkout — unfamiliar networks, wallet confirmations, irreversible sends. If the page looks like an anonymous gateway with a generic blue header, you absorb all that friction alone. If it looks like your website — your logo, your color, your company name — you borrow trust you already earned elsewhere.

Settlematic ships first-class merchant branding: upload a logo, pick a brand color, set your company name once in Settings → Branding, and every hosted payment page and PDF invoice reflects that identity. This article explains why branding is a differentiation factor for crypto invoicing platforms, what we render where, configuration steps, and design practices that make B2B merchants look premium without a custom engineering project.

Why branding matters more in crypto payments than card checkout

Card checkout benefits from network effects: Visa logo, issuer name, 3-D Secure flows, chargeback rights. The payer feels protected by institutions. Crypto push payments remove that cushion. The client sends from their wallet to an address your invoice generated. Phishing awareness is high — rightly so. A polished, consistently branded experience signals legitimacy: this invoice really came from the agency you hired, not a lookalike domain.

We measured merchant feedback (qualitative, n≈40 onboarding calls in Q1–Q2 2026): clients complete payment faster when the hosted page matches the merchant's site aesthetic. Finance leads report fewer 'is this link safe?' support tickets when logo and color match proposal PDFs sent during sales. Branding is not vanity — it is conversion and support-cost reduction on high-trust actions.

What Settlematic branding covers today

• Company name displayed on PDFs and payment pages when logo absent
• Logo upload — PNG, JPG, or WebP up to 2 MB, stored per organization
• Brand color as hex — drives accents on PDF header bar, labels, and hosted UI
• Hosted payment pages at settlematic.com/pay/{token} — no client account required
• PDF invoices and receipts downloadable from merchant dashboard and client payment page
• Branded email notifications when invoices are sent (logo in template context)

Branding is org-wide. One configuration applies to all invoices — consistent with how small and mid-size merchants actually operate. Enterprise white-label domains are a common roadmap request; today we optimize for speed-to-professionalism, not full domain CNAME customization.

Hosted payment page: where trust converts

The hosted page is where money moves. It shows invoice number, line items, fiat total, crypto quotes per allowed asset, rate validity countdown, QR codes, and payment status timeline. Your logo appears in the header; brand color tints buttons, badges, and progress indicators. Clients on mobile scan QR codes without reading URLs — visual brand continuity reassures them they are in the right place.

Contrast with unbranded crypto requests: a bare address in Telegram could belong to anyone. Branded pages tie the payment action to a document with INV- number, due date, and merchant identity. That document linkage is what accountants want; the branding is what clients feel.

PDF invoices: the artifact clients keep

B2B clients file PDFs. Auditors ask for them. Procurement portals upload them. Settlematic generates PDFs server-side with jsPDF: a top brand-color bar across the page, your logo scaled proportionally (max width 48mm, height 14mm), invoice or receipt label in brand color, line item table, tax breakdown, totals, and payment terms. If logo upload fails or is absent, company name renders as text header — never a blank identity block.

Merchants preview PDF styling in the invoice editor before send. Clients download PDF from the payment page after confirmation — receipt variant includes paid timestamp. Same branding pipeline for both — no 'ugly system PDF' vs 'pretty hosted page' split that erodes trust.

How to configure branding (step by step)

Sign in as org admin → Settings → Branding. Enter company name exactly as it should appear on legal documents. Upload logo: square and horizontal marks both work; we preserve aspect ratio. Pick brand color with the hex picker — default is #2563EB if you skip. Save. Create a test invoice on testnet and open the hosted link in an incognito window to see client view without merchant session cookies.

• Use PNG with transparent background for logos on white PDF headers
• Avoid ultra-light pastel brand colors on white — contrast matters for accessibility
• Re-upload logo if you refresh brand — old URLs invalidate on replace
• Match email proposal PDFs to Settlematic colors for cognitive consistency
• Test mobile — logo max height keeps headers from pushing payment CTA below fold

Differentiation vs generic crypto payment links

Payment link products optimize for anonymous checkout — same UI for every merchant. That is fine for donations. It is lethal for $25k consulting invoices. When every vendor's link looks identical, clients default to slow approval chains. Branded invoicing platforms let you carry sales-call professionalism through to settlement.

Settlematic's combination — fiat-quoted invoice structure, multi-chain checkout, non-custodial sweeps, and merchant branding — targets service businesses billing other businesses. Branding is the visible half of that story; audit trails are the invisible half. Competitors may offer one without the other. Merchants choosing Settlematic often cite 'clients take us seriously' as the qualitative win, not a specific chain count.

Premium brand perception without a design team

Premium is consistency, not ornament. A single brand color used discipline across PDF bar, hosted Pay button, and status chips beats a cluttered template with stock photography. Agencies with strong identity guidelines onboard in ten minutes: export logo SVG → convert to PNG → upload → set hex from brand book → done.

Recurring retainers amplify branding value. Month six invoice looks like month one. Clients subconsciously trust stable presentation — especially when amounts are large and payment method is unfamiliar. Pair branding with clear payment states (waiting, confirming, confirmed) so clients never stare at a spinner on a page that looks phishy.

Technical details merchants ask about

Logo files upload to object storage keyed by organization ID. Payment and PDF services resolve public CDN URLs at render time — no embedded binary in invoice rows. Brand color stores as hex on the organization record; PDF generation converts to RGB for jsPDF fill and text colors. Hosted React payment components read the same branding payload from pay-page API responses — single source of truth.

Cache implications: after branding change, open invoices reflect new logo on next page load. PDFs generated before change keep prior render until regenerated — finance should re-download if they cached old files locally. Client bookmarks to /pay/{token} always fetch current branding.

Accessibility and trust signals beyond color

Brand color alone does not meet WCAG if contrast fails. We recommend testing button text against brand color with a contrast checker. Hosted pages also show network badges, explorer links, and explicit asset labels — transparency features that complement branding. Clients trust 'professional plus provable' — logo establishes who, explorer link establishes what happened on-chain.

Include support email in invoice notes defaults so clients see a contact path on PDF footer. Branding plus contact plus invoice number triangulates legitimacy better than any single element.

Common mistakes during onboarding

• Uploading low-resolution logo — blurry header undermines premium positioning
• Neon brand color on white PDF — unreadable 'INVOICE' label
• Skipping testnet preview — discover mobile layout issues with real logo too late
• Different company name spelling on branding vs contract — client confusion in AP systems
• Relying on default blue — fine for dev, signals 'unconfigured' to clients in production

Branding in the sales and renewal cycle

Sales teams send proposals. Delivery teams send invoices. If proposals are polished Canva or Keynote decks but invoices are plain text wallet addresses, you create a discontinuity clients notice. Settlematic lets you align hex color and logo with proposal templates in one settings screen — procurement sees the same identity from signature to settlement.

For renewals, branded PDF receipts archive cleanly in client finance systems. When renewal season arrives, their AP team searches vendor name — your logo mark appears in historical PDFs, speeding approval for next year's retainer.

How branding interacts with other Settlematic features

Recurring schedules auto-generate branded invoices each cycle — no manual re-application. Bulk CSV imports inherit org branding on every created row. MCP create_invoice returns paymentUrl and pdfDownloadUrl reflecting current branding even when creation happened from Claude. Webhooks do not include logo binary — consumers pull PDF URL if needed.

Conversion flows and sweep settings are treasury-back-office concerns — clients never see them. Branding is front-office. Keeping that separation clear helps merchants reason about what affects client trust vs internal ops.

Before and after: client perception

Before branding: client receives plain email with amount and link. Page shows Settlematic layout with default blue accent. AP clerk asks finance to confirm vendor legitimacy. Payment delayed until verbal confirmation from account manager.

After branding: same email structure, but hosted page shows agency logo and burgundy accent from pitch deck. PDF attachment preview (if sent) matches. AP clerk files without escalation. Payment same day. The on-chain risk did not change — perception of vendor authenticity did.

Industry-specific notes

Consultancies and law firms care most about PDF gravitas — serif-friendly logos and conservative colors perform well. Creative studios push bold colors; ensure Pay button text stays white or black with sufficient contrast. Web3 agencies often have dark-mode brand sites; remember hosted pages default light — choose brand colors that work on white backgrounds or adjust logo variant to dark-on-light.

Marketplace sellers and NFT studios frequently run high-volume lower-ticket invoices. Branding still matters at scale — buyers recognize repeat vendors faster in wallet history when visual identity is consistent across drops.

Internal alignment: sales, finance, and delivery

Branding settings should be owned by marketing or ops with finance read access — not every developer uploading a favicon. Document hex code in brand guidelines PDF. When sales uses #1A1A2E and invoices ship default blue, clients notice. One settings screen prevents organizational drift.

Delivery leads sending milestone invoices should not screenshot hosted pages for clients — send the official link so branding, status updates, and receipt downloads stay authoritative.

Roadmap transparency

Merchants ask for custom domains (pay.yourcompany.com), multiple brand profiles per business unit, and per-client co-branding. We do not ship those in v1. Documenting limits honestly prevents churn from wrong expectations. Today's branding target is: one org, one identity, consistently on every client touchpoint we control — hosted page, PDF, and send email.

Checklist before first production invoice

• Logo uploaded and sharp on retina mobile
• Brand color meets contrast on Pay button and PDF header
• Company name matches contract entity
• Testnet invoice paid end-to-end in incognito
• PDF downloaded and filed in sample client record
• Support contact in default invoice notes

Treat branding as part of go-live checklist alongside sweep destinations and testnet rehearsal — not a post-launch polish task. Merchants who configure identity before the first mainnet send consistently report smoother client adoption in onboarding interviews we conduct monthly.

If you are evaluating crypto invoicing vendors, ask to see a hosted payment page and PDF sample with branding enabled — not just a feature checklist. The quality of those two artifacts predicts how your clients will experience settlement. Settlematic invests in both because crypto push payments demand every trust signal you can earn without a card network backing you.

Bottom line

Crypto invoicing competes on treasury architecture and finance features — but clients experience your brand before they experience your sweeps. Custom logo and color on hosted pages and PDFs is one of the fastest ways Settlematic merchants differentiate from generic payment links and look premium relative to competitors still shipping unbranded checkout.

Configure branding before you send your first mainnet invoice. Ten minutes in Settings → Branding buys disproportionate trust on every payment link you will ever send. Your clients already decided to hire you — show them the same company at checkout that they hired during sales.