Skip to main content
All systems operationalChangelogv1
Log in
Payment Link setup

Customize Payment Links

Choose the branding, checkout modules, customer fields, link controls, and return experience used by DEUNA Payment Links.

On this page

Use this guide to decide what to customize and where to configure it. A Payment Link combines merchant-level defaults, settings on an individual link, and the visual rules supported by CustomStyle.

Choose the correct control#

Merchant defaultsSet the baseline brand, locale, hosted domain, modules, and customer-data requirements used by Payment Links.TAM · Account configurationIndividual linkChoose products, payment methods, modules, limits, expiration, and return destinations for a specific link.Admin · APICustomer-facing UIAdjust supported colors, typography, copy, and checkout views without redefining the Payment Link flow.CustomStyle
GoalConfigure it inDetailed guide
Establish logo, primary color, locale, or hosted domainMerchant configuration with your TAMThis page
Enable login, customer information, billing, or order summaryMerchant defaults or supported checkout_modules on the linkWidget settings
Set products, payment methods, expiration, purchase limits, or retry limitsDEUNA Admin or Payment Link APIManage Payment Links or Payment Link via API
Change supported checkout copy and visual stylingCustomStyleCustomStyle overview
Send the customer to a merchant page after an outcomeSupported return URLs on the linkPayment Link via API
Confirm the authoritative payment resultBackend retrieval and webhooksWebhooks

Set merchant defaults#

Work with your TAM to define the baseline experience inherited by Payment Links. Confirm each setting for the merchant and environment where the link will run.

Brand, locale, and hosted URL

The baseline presentation can include:

  • business logo, alignment, and size;
  • the primary action color;
  • the default customer-facing language; and
  • the hosted Payment Link domain assigned to the merchant.

Keep sufficient contrast for buttons and status text, use an image that remains legible on narrow screens, and test the configured locale with real product and payment-method labels.

Checkout modules and customer data

Modules determine which screens and information the customer encounters. The same modules are documented for the wider checkout experience, so their field rules remain centralized in Widget settings.

ModulePayment Link purpose
LoginPatternRecognize a returning shopper and start the supported one-time-password flow.
UserInfoPatternCollect the customer identity and contact fields required by the merchant.
BillingPatternCollect billing information in the main checkout or a separate view.
OrderDetailPatternShow the products and amount breakdown associated with the order.
Example Payment Link with customer information, payment method, billing fields, and order summary.

For billing information shown directly on the main checkout, configure no more than four fields. If the order already contains billing data, the customer can see a summary instead of an empty form. Put country before state or province and city when those dependent fields are collected.

Identity-document collection is part of the payment and customer-data configuration. Use the identity-document reference to review the supported document labels before requesting it.

Choose the creation path that owns the link:

Create in DEUNA AdminCreate and edit products, pricing, payment methods, expiration, usage limits, and result-page behavior from the Admin interface.Create through the APISend the supported order, payment-option, module, configuration, and return fields from a merchant backend.

An API-created link can include these groups of settings:

Setting groupWhat it controls
Order and itemsCustomer-visible product names, quantities, prices, taxes, discounts, and images.
Payment optionsThe payment methods and compatible processors offered for that link.
checkout_modulesSupported modules such as LoginPattern, UserInfoPattern, and OrderDetailPattern. Merchant defaults apply when this field is omitted.
configurationLink name, expiration, completed-purchase limit, and payment-retry limit.
redirect_urlsSupported customer destinations for success, pending, error, close, or fallback behavior.

Do not use a browser return as proof of payment. A customer can close the page, lose connectivity, or return while the provider result is still pending. Preserve the order token and confirm the final state through backend retrieval or DEUNA webhooks.

Style the customer-facing UI#

Use CustomStyle for supported visual and text overrides. It applies to DEUNA checkout surfaces; it does not change which modules are enabled or which fields the Payment Link API accepts.

Theme and brandingSet supported colors, typography, shape, and base visual tokens.Customer and billing viewsCustomize customer-field labels, then continue to the linked billing-data view.Payment outcomesCustomize the thank-you view and related result-state experiences.

Open the CustomStyle overview to select a checkout area, preview it, and assemble one consolidated object. Check each focused guide for Payment Link limitations; not every widget-only element appears in the hosted Payment Link experience.

Verify the experience#

Before sharing a production link:

  1. Open the link on desktop and a narrow mobile viewport.
  2. Confirm the logo, contrast, locale, product information, totals, and enabled payment methods.
  3. Complete guest and returning-customer flows when login is enabled.
  4. Validate every required customer, identity, and billing field for the target country.
  5. Test success, pending, rejection, close, and expired-link behavior.
  6. Confirm that each browser destination works and that your backend still receives or retrieves the authoritative payment result.

Continue#

Payment Link overviewReview the hosted experience, creation paths, and security behavior.Manage Payment LinksCreate, edit, deactivate, and monitor links in DEUNA Admin.CustomStyle referenceLook up supported visual and customer-facing copy properties.