Implement the official Nicky crypto payment button in my project. Button type: With asset icons Framework: {{FRAMEWORK}} Variant: {{VARIANT}} Height: {{HEIGHT}} px Width: {{WIDTH}} Action: {{ACTION}} Label: {{LABEL}} Locale: {{LOCALE}} Your Nick: {{RECEIVER}} Checkout URL or existing callback: {{CHECKOUT}} Use the Nicky style guide at https://nicky.me/branding-guidelines/payment-button/ and the nicky-crypto-button skill when available. Preserve the original N monogram, its proportions and the supplied component color and size values. Use the selected action label and locale exactly. Support English, Brazilian Portuguese, Greek, Spanish, French, Russian, Vietnamese and Nepali for all action presets. Set the button's lang attribute to the selected locale. The legacy Crypto action uses Nicky's existing product wording in these same locales. Use Your Nick (email, verified domain or Short ID) to fetch supported crypto assets connected to that Nicky account from userAssetConnections, deduplicated by ticker, and use their supplied icon files. Resolve an email or domain to its matching Short ID through the existing public Nick/search endpoint before requesting payment data; the payment-data endpoint accepts only Short IDs. Show connected assets in sequence, then rapidly return to the N monogram with a mechanical split-flap animation. Respect reduced-motion preferences. Do not show an asset count. Never render an asset row below the button. Never use acceptedAssets pricing currencies for these icons. The selected verb changes the label only; connect the matching existing flow supplied by the integrator. Use only the confirmed public Nick/search and payment-data endpoints and existing supplied icon files. Implement visible keyboard focus, keyboard operation, disabled state and accessible status announcements. Do not add a loading animation. Accessible naming must include both action and Nicky. Payment destinations must never open signup. Connect only the checkout URL or existing callback supplied above. Do not invent endpoints, packages, authentication, credentials, or payment confirmation behavior. Identify any missing data required to connect the existing checkout. Report the files changed and how to verify the result. See the API reference at https://api-public.pay.nicky.me/swagger/index.html.