Payment button

A recognizable Nicky action for crypto checkout. Choose an appearance, preview the button and copy the code for your existing payment flow.

One action, clearly identified

Choose a plain button or preview the assets connected to a Nicky account. With assets enabled, the button shows each supported icon in sequence, then quickly flips back to the N monogram. Both live examples open NICKY's existing checkout in a new tab; no payment is submitted automatically.

Button type

The preview and generated button label use the selected language. Languages match Nicky's production app.

HTTPS checkout URL validated.

The initial example opens NICKY's live checkout in a new tab. Before integrating, replace the checkout URL with your own. The plain button does not need a Nick. The example does not submit or confirm a payment.

DEMO PREVIEW

Plain button code

Plain button prompt

Download prompt

Three button variants

Dark, lime and light styles from the current button kit. Each uses the same neutral preview background.

Dark buttonPay with Nicky
Lime buttonPay with Nicky
Light buttonPay with Nicky
Pay with NickyPay with NickyNormal, lime and disabled preview

Interaction states

HoverPay with Nicky
Keyboard focusPay with Nicky
PressedPay with Nicky

Accepted-asset icons

This example loads supported crypto assets from the Nicky account entered as Your Nick using the existing payment-data API. It shows each connected asset in sequence, then quickly flips back to the N monogram. The table lists the networks connected to that account.

Connected assets for NICKY

The button shows each asset connected to this Nicky account in sequence, then quickly flips back to the N monogram. The table shows the connected assets and their networks. The button opens the existing checkout in a new tab; it does not submit or confirm a payment.

Pay with NickyExample checkout for receiver NICKY

If an asset has no bundled icon, it is omitted. If the lookup fails, the payment action remains available without icons. See the crypto icon guide for files and usage details.

Fits into the payment moment

Try the same live NICKY checkout from different surrounding layouts. Each button opens a new tab; payment details are entered in Nicky's own flow.

Layouts, order references and amounts are illustrative; they are not passed to the live checkout. Checkout and product examples use the plain button; the invoice example shows asset icons.

Button style guide

The values below describe this component's implementation. For other logo placements, follow the specifications supplied with the approved artwork. Keep the mark intact and the complete action readable.

Color
Dark: #121212 background with #B7FF43 text. Lime: #B7FF43 background with #121212 text. Light: #FFFFFF background and #121212 text with a dark border. Keep the preview canvas #F5F4F0 for every variant.
Type
Inter at weight 600, 14px for 44px and 48px buttons, 15px at 56px. Use the system sans-serif fallback.
Size and spacing
Minimum heights are 44px, 48px and 56px. One connected 18px asset icon, or 20px at size 56, replaces the N mark. Show supported account assets in sequence, then quickly flip back to the N monogram. Keep 10px between the mark and text.
Clear space
Keep clear space around the asset and between neighboring controls. For placement-specific measurements, follow the specifications supplied with approved artwork.
Mark proportions
Use the supplied PNG at its natural square ratio. Do not stretch, recolor, crop or replace it with typed text.
Background choice
Keep button preview backgrounds at #F5F4F0 regardless of the selected button variant.
Mobile
Use 44px or taller. Container width is available where the checkout layout benefits from a full-width action. Let supporting content reflow at 200% zoom.
Button labels
The pay, donate, send, buy and tip presets follow the selected language: English, Brazilian Portuguese, Greek, Spanish, French, Russian, Vietnamese or Nepali. The legacy “Pay with Crypto” option uses Nicky's existing wording for those languages. The Version 1.0 Brand Guidelines still specify the legacy wording; these presets reflect the subsequent product direction. “Powered by Nicky” is the recommended secondary signature. A payment button must never open a signup page. Your Nick can be an email, verified domain or Short ID. The button loads supported asset icons from that Nicky account; only locally supplied icon files are shown.

Good: original mark and full label

Keep both action and provider visible.

Avoid: distorted mark

Pay with Nicky

Stretching changes the supplied mark.

Avoid: weak contrast

Pay with Nicky

Use only the published foreground and background pairs.

Avoid: clipped label or tight spacing

Pay with Nicky

Reserve space for the complete translated action.

Connect your existing checkout

The button starts or opens your payment flow. Your integration owns payment creation and confirmation.

  1. Choose Plain button or With asset icons, then select the text, language, variant, height, width and code format.
  2. Enter the HTTPS checkout URL supplied by your integration.
  3. Copy the example and save the CSS and official mark beside your application files, following the paths in the snippet. The five action presets use the selected language. Only the asset version needs Your Nick; the plain version has no asset lookup.
  4. Keep hover, pressed and keyboard focus feedback clear. The component preserves its accessible busy state without a loading animation. Confirm payment through your own payment system.

The URL must use HTTPS and must not contain credentials. No credentials belong in browser code. See the existing Nicky API documentation for API details.

Downloads and AI implementation

The kit includes separate plain and asset-icon examples. Choose the matching code and prompt in the configurator, or give the self-contained skill to an agent that supports local skills.

Extract the skill ZIP. Copy its top-level nicky-crypto-button folder into the local skills directory accepted by your agent, then start a new agent session and ask it to use the skill. Supported skill directory locations differ by tool, so use that tool's own documentation. The skill does not require a registry or install command.

Skill file: SKILL.md. Official mark: n-mark.png. Canonical public guide: https://nicky.me/branding-guidelines/payment-button/.