Pay by Link
Programmatic invoice settlement requires a robust pay by link api that integrates directly with existing enterprise resource planning systems. Cardflo enables operations teams to automate payment requests, dispatching secure URLs via email or SMS for exact invoice amounts.
- Category
- Checkout
- Capabilities
- 6
- Available on
- All plans
Enterprise operations and technical teams require programmatic methods to collect payments for specific invoices, telephone orders and subscription renewals. Manual link generation creates unacceptable operational overhead, while email and SMS payment requests demand exact transaction mapping to clear outstanding balances within existing corporate finance software.
Cardflo handles programmatic URL generation by integrating directly into core operational software, routing these requests to suitable acquirer partners. The system creates automated payment links containing precise order references, allowing merchants to dispatch payment prompts securely while capturing real-time settlement data to close pending accounting records.
Cardflo's Pay by Link functionality generates secure, trackable payment URLs for invoices, SMS, and chat, simplifying remote collections. This feature improves the success rate of payments made outside of a traditional checkout environment, boosting operational efficiency.
Pay by Link overview
Connecting billing software to payment infrastructure demands precise API integration rather than manual dashboard intervention. Cardflo focuses entirely on the automated generation of an invoice payment url, connecting enterprise resource planning tools directly to a global acquirer partner network.
The architecture captures the transaction value, order reference and customer identifier programmatically, generating a unique destination for the buyer to complete the purchase. This approach ensures that high-volume operations can dispatch thousands of requests simultaneously via automated workflows.
Merchants requiring manual dashboard link creation must use the payment links module, while those building an on-site checkout UI should integrate an embedded checkout widget, and smartphone-specific flows rely on mobile-optimised checkout. By treating URL generation as an automated data exchange, finance teams secure exact reconciliation for every issued invoice.
How pay by Link works
API request initiation
The merchant system transmits a secure server-to-server request containing the required transaction amount, currency code and internal order reference. The Cardflo orchestration engine receives this payload, verifies the merchant credentials and prepares the transaction data for routing. This initial communication establishes the foundational data required to track the specific payment through the complete lifecycle.
Programmatic URL generation
Cardflo translates the received payload into a unique, single-use URL. The platform determines the optimal acquirer partner for the specific currency and sector, assigning the routing logic to the link before returning the secure string to the merchant software. The merchant system then dispatches this link automatically via email or SMS directly to the end customer.
Real-time reconciliation webhooks
Once the customer navigates to the URL and completes the transaction, Cardflo captures the outcome from the acquirer partner. The platform immediately fires a webhook back to the merchant infrastructure containing the precise order reference and settlement status. Finance operations use this automated data feed to close outstanding invoices and trigger subsequent fulfilment processes automatically.
Why pay by Link matters
Automated ledger management
Manually matching incoming bank transfers or generic card payments to specific invoices creates significant administrative delays. Generating URLs programmatically ensures that every received payment carries its exact original order reference. Finance departments eliminate suspense accounts and manual reconciliation tasks, as the payment data automatically updates the corresponding billing record upon successful authorisation.
Call centre payment security
Telephone operators collecting card details verbally increase compliance risk and operational complexity. By adopting automated call centre payment links, agents can trigger a secure URL via email or SMS while remaining on the phone. The customer enters their sensitive credential into a secure browser session, completely removing the merchant infrastructure from direct payment data exposure.
Regulatory notes for pay by Link
PCI DSS scope for payment URLs
Generating transaction URLs programmatically ensures that sensitive primary account numbers never traverse the merchant's internal servers or customer relationship management databases.
By offloading the collection interface to a secure Cardflo environment, operations teams significantly reduce their compliance scope, specifically concerning telephone agent environments and internal corporate networks.
This architectural separation allows qualifying merchants to complete simpler self-assessment documentation for their annual compliance audits.
The Cardflo platform tokenises the financial data upon collection, transmitting only the secure token and the final authorisation status back to the merchant infrastructure for safe long-term storage and subsequent billing cycles.
3DS2 authentication within payment URLs
All URLs generated through the Cardflo API automatically support the latest 3D Secure protocols required under the European Union's Revised Payment Services Directive.
When a customer accesses the link to settle an invoice, the platform evaluates the transaction risk and prompts the user for multi-factor authentication if mandated by the issuer.
The orchestration layer manages the necessary redirect flows between the buyer's browser and their issuing bank.
By handling these complex authentication steps within the secure URL environment, merchants ensure compliance with Strong Customer Authentication mandates without needing to build or maintain complex verification logic within their own enterprise software applications.
Pay by Link use cases
ERP invoice link generation
An ERP requests a single-use payment URL for each approved invoice, carrying the invoice number, customer account and exact amount without exposing card data. Cardflo returns the hosted URL through the API and sends payment status references into reconciliation workflows so finance teams can match settlement against the originating ledger entry.
Call centre balance collection
A call centre agent triggers a time-limited payment link from the CRM while discussing an outstanding order balance, avoiding spoken card details and agent access to credentials. Cardflo hosts the card entry flow, applies 3DS2 where required and returns the result to the customer record through API callbacks.
Order amendment payment links
An operations system calculates an additional amount after a customer changes quantities, delivery options or specifications on an existing order. Cardflo generates a secure URL tied to the original order identifier, then reports authorisation and payment status back to the order management system before revised fulfilment is released.
Automated arrears payment requests
A collections platform inserts account-specific payment URLs into scheduled SMS or email reminders, with each link fixed to the current arrears balance and case reference. Cardflo supports API generation, expiry controls and webhook notifications, enabling collection teams to stop further reminders and reconcile cleared payments against the correct debtor account.
Pay by Link by the numbers
Industry observations suggest that once a customer reaches a secure hosted link, completion rates typically fall within this range depending on the merchant sector.
Businesses moving from manual phone payments to hosted links often see a significant reduction in the number of security controls they must personally manage.
Typical processing time from the moment the 'Pay' button is clicked until a confirmation appears, assuming standard gateway and acquirer performance.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Pay by Link
- Generates unique transaction URLs programmatically to eliminate manual data entry during high-volume invoice processing.
- Connects customer relationship software to acquirer partners through a secure crm payment integration layer.
- Injects exact transaction values and order identifiers into URLs to ensure accurate automated ledger reconciliation.
- Supports expiration parameters on individual URLs to enforce strict payment deadlines on pending digital invoices.
- Facilitates multi-channel distribution by returning standard strings formatted for email, SMS or automated ticketing platforms.
- Routes transactions dynamically to the most appropriate acquirer partner based on the customer's geographic location.
A short scoping call, then a written plan for your MIDs.
Questions about Pay by Link
How does the API manage URL expiration times?
Merchants can define explicit expiration parameters within the initial API request payload. The system accepts ISO 8601 formatted timestamps, rendering the URL inactive once the specified deadline passes.
If a customer attempts to access an expired link, the platform displays a customisable standard error page instead of a payment form.
This control proves essential for time-sensitive travel bookings, flash sales or strict invoicing terms, ensuring that customers cannot submit a payment for an expired quotation or a cancelled digital order.
Can the generated URLs support multiple payment methods?
The Cardflo orchestration engine evaluates the incoming API request to determine available payment options based on the target currency and market.
When the customer opens the generated URL, the platform displays appropriate local methods such as iDEAL, SEPA or digital wallets like Apple Pay and Google Pay alongside standard card options.
The orchestration logic applies merchant-defined routing rules behind the scenes, directing the chosen payment method to the correct acquirer partner without requiring any further input from the customer.
What happens when a customer partially pays an invoice?
The standard programmatic link enforces exact settlement of the requested amount, preventing underpayment or overpayment discrepancies in the billing system. If a merchant wishes to allow partial payments, their internal billing software must calculate the new balance and request a fresh URL via the API.
This architecture ensures that the payment gateway always processes a fixed, verifiable amount, keeping the merchant ledger perfectly synchronised with the acquirer partner settlement files and avoiding complex partial reconciliation logic.
How does the system handle webhook delivery failures?
Cardflo employs a robust retry mechanism for all asynchronous webhooks detailing transaction outcomes. If the merchant server fails to acknowledge the webhook with a 200 OK HTTP status code, the system queues the message and initiates an exponential backoff schedule.
Technical teams can also query the transaction status API directly using the original order reference to manually fetch the payment outcome. This dual approach ensures that finance software eventually receives the settlement confirmation, even during temporary network outages.
Related features.
Related guides.
See how Cardflo compares.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.