Salesforce Pay Now: Customize payment links and extend with payment APIs

Are you ready to transform rigid payment links into strategic revenue accelerators?

In today's fast-paced markets, businesses face a critical challenge: overdue invoices erode cash flow while customers demand seamless, branded payment experiences. Salesforce Pay Now emerges as a powerful solution, enabling you to generate unique or reusable payment links that direct customers to customized Pay Now payment pages—like digital invoices that capture payments instantly without complex e-commerce setups.[9][14][18]

Consider the tension many developers encounter during implementation: the perception of being locked into OOTB (Out of the Box) look and feel and functionality. While Salesforce Pay Now prioritizes rapid deployment via the Commerce Setup Assistant—available standalone with a Salesforce Payments license—this doesn't mean sacrificing control.[6][10][16] Here's where strategic thinking unlocks value:

• UI and Experience Customization: Use Experience Builder to tailor the payment section in checkout flows for B2B or D2C stores. Add Salesforce Payments components, enable express payments (Apple Pay, Google Pay, PayPal), or integrate digital wallets—but only with custom checkout, not managed flows. For collections, customize prebuilt flows to let specialists send branded links.[2][4][12]

• Payment Processing Flexibility: Beyond OOTB, expand with tax and shipping options via "Checkout with Order" links, auto-creating order records for integrated management. Support recurring payments, direct debit (SEPA, ACH), or gateways like Stripe/PayPal, with dynamic forms that adapt to your Salesforce org configuration.[1][5][6]

• API-Driven Integration and Development: Unlock deeper customization through Salesforce Pay Now APIs and Payment APIs. Query available payment methods, processors, and source connectors (e.g., Nonprofit Success Pack) via endpoints like /PaymentMethods. Build dynamic submission forms, handle redirects for card details, and confirm transactions end-to-end. For B2C Commerce, leverage SalesforcePaymentRequest for Pay Now or Buy Now buttons, configuring options like auto-capture or saved payments.[1][3][7][15]

Yet, a provocative reality check: True extensibility demands the right licenses—Salesforce Payments alone suffices for basic Pay Now setup and predefined links, but pairs with Commerce for advanced features like blended pricing or order checkouts.[6] Developers often overlook developer resources like the API Library, Payment object references, and PaymentLink objects, which expose endpoints for tokenization and system integration without native card storage.[11][13][17]

The strategic insight? Salesforce Pay Now isn't just a feature—it's a payment gateway pivot for Salesforce platform mastery. Move beyond technical documentation gaps by combining OOTB configuration with APIs for user interface personalization and payment processing automation. Imagine reducing DSO by 30% through frictionless links embedded in apps, emails, or social—while maintaining PCI compliance and fraud protection.[1][6][19]

What if your next implementation prioritized business agility over pixel-perfect code? Explore these reference materials to prototype: Start with informational endpoints for real-time functionality discovery, then scale to custom flows that align integration with revenue goals. Your customization journey begins with questioning the constraints—because in Salesforce, OOTB is merely the launchpad.[1][2][3]

What is Salesforce Pay Now and how do payment links work?

Salesforce Pay Now lets you create unique or reusable payment links that send customers to branded Pay Now payment pages (digital-invoice style) to capture payments without a full e‑commerce setup. Links can be embedded in apps, emails, or social channels and support immediate payments, tokenization redirects, and end‑to‑end transaction confirmation through the PaymentLink/Payment APIs.

Do I need Salesforce Payments or Commerce to use Pay Now?

A Salesforce Payments license is sufficient for basic Pay Now setup and predefined payment links. If you need advanced commerce features—like blended pricing, order checkouts, or full B2C Commerce flows—you'll pair Salesforce Payments with Commerce functionality or licensing.

Can I customize the look and experience of Pay Now pages?

Yes. Use Experience Builder to tailor the payment section in custom checkout flows and add Salesforce Payments components. For collections and specialist‑sent links, you can customize prebuilt flows to preserve branding. Note: express payments and some wallet features require custom checkout—managed (OOTB) flows are more limited.

Which payment methods and processors are supported?

Salesforce Pay Now supports card payments, express wallets (Apple Pay, Google Pay), PayPal, direct debit schemes (SEPA, ACH), recurring payments, and third‑party gateways like Stripe via connectors. Available methods depend on your org configuration, enabled processors, and integration choices—queryable via endpoints like /PaymentMethods.

How do APIs factor into custom Pay Now implementations?

Salesforce provides Payment APIs (Payment, PaymentLink, /PaymentMethods, SalesforcePaymentRequest for B2C Commerce) to discover available methods/processors, create links, build dynamic submission forms, handle card tokenization redirects, and confirm transactions. These APIs let you combine OOTB configuration with deep customization and automation.

Are card details stored in Salesforce?

Salesforce does not store raw card data in standard Payment objects. Tokenization and processor redirects are used so card data is handled by the connected processor or token service, helping you meet PCI requirements while enabling saved payment sources where supported (via processor tokens, not native card storage).

Can Pay Now create orders or support shipping and tax?

Yes—using "Checkout with Order" links you can auto‑create Order records so payments, tax, and shipping are integrated into your Salesforce order flow. This is typically used when you need blended pricing, order reconciliation, or closer commerce orchestration with payments.

How do express payments and digital wallets work with Pay Now?

Express payments (Apple Pay, Google Pay) and some wallet integrations are supported but generally require custom checkout flows where you can add the appropriate Salesforce Payments components. Managed/fully‑managed OOTB flows may not expose these wallet integrations.

Can I support recurring billing and direct debit via Pay Now?

Yes. Salesforce Payments supports recurring payments and direct debit schemes (for example SEPA and ACH) when your payment processors and legal setup allow. Use the payment APIs and tokenization flows to create saved mandates/tokens for future charges where supported by the processor.

How do I integrate third‑party gateways like Stripe or PayPal?

Integrate via supported payment processors/connectors or custom API integrations. Configure the processor in Payments, query available methods with endpoints like /PaymentMethods, and implement tokenization/redirects per the processor's model. Some connectors (e.g., Stripe, PayPal) are prebuilt; others require custom work.

What developer resources should I use when building Pay Now solutions?

Start with the Salesforce API Library, Payment and PaymentLink object references, and the Commerce/Payments developer docs. Use informational endpoints to discover enabled features in your org, prototype with SalesforcePaymentRequest for B2C Commerce, and follow tokenization and security patterns in the docs for PCI compliance.

How can Pay Now help reduce Days Sales Outstanding (DSO)?

By embedding frictionless, branded payment links in invoices, emails, apps, or social channels and supporting express wallets and one‑click pay flows, you can accelerate collection velocity. Organizations report meaningful DSO reductions by simplifying payment paths and automating reconciliation through linked Order/Payment records.

What are common limitations or gotchas to watch for?

Expect differences between OOTB managed flows and fully customizable checkouts (wallets and advanced UX often need custom checkout). Ensure you have the right licenses for desired features, confirm processor support for recurring/direct debit, and design around tokenization (cards aren't stored natively). Also plan for fraud protection and regional compliance (e.g., PSD2/SCA).

What's a recommended rollout approach for custom Pay Now functionality?

Prototype quickly with the Commerce Setup Assistant and informational API endpoints to see enabled capabilities. Then iterate: add Experience Builder customizations, integrate payment APIs for tokenization and order creation, and expand to express wallets or recurring flows once processor and licensing requirements are validated. This balances speed with extensibility.