Online and offline sales
Get paid for products or services across any sales channel.
Payment methods
Pay by Link: get paid easily and securely
Generate personalised, encrypted payment links and send them by email, SMS or any channel. Your customers pay in an instant, from their phone or computer — no online store required.
What is Pay by Link?
It's a solution that lets you generate personalised payment links to get paid online. Just send the link to your customer, who pays quickly and securely from their device.
For you
Flexibility
Send payment links to any customer, anywhere.
Simplicity
Generate links in seconds, with no complex integration.
Security
Each transaction uses a unique, encrypted URL.
Full control
Track the status of transactions in real time.
For your customers
Ease
Fast, intuitive payments from a phone or computer.
Security
Data protected with end-to-end encryption.
Convenience
They pay anywhere, anytime.
Use Pay by Link for
Invoices and receipts
Make it easy to pay your invoices.
Donations
Receive donations quickly and securely.
Professional services
Get paid for your services conveniently.
Available payment methods
Multibanco references, MB WAY, Payshop references and direct debits. Coming soon: credit cards, debit cards, Apple Pay, Google Pay and Pix.
Frequently asked questions
What is Pay by Link?
Pay by Link lets the Client generate a payment link and send it to the Payer by email, SMS, messaging apps or other digital channels. When the Payer opens the link, they reach a secure page where they can review the operation's details and choose one of the available payment methods.
In which situations can it be used?
The service can be used to receive payments, including payments for orders, services, bookings, registrations, invoices or other amounts owed to the Client.
Does the Payer need to create an account?
No. The Payer only needs to open the link they received and follow the instructions shown on the payment page.
How can the Client generate a payment link?
The link can be generated using the tools made available by lusopay, or through an integration with the Client's own systems. The integration must follow the applicable technical documentation.
Where does the link become available after it's generated?
When the link is created through the Client Area, the Client can copy it or send it to the Payer using the available options. In an integration, the address is returned to the Client's system in the response to the generation request.
Amount, validity and use
Can the payment amount be set in advance?
Yes. The Client can generate the link with an amount defined beforehand. When the open-amount feature is available and used, the Payer will be able to enter the amount on the payment page.
Can the link expire?
Yes, in API integrations. The validity period depends on the configuration chosen at generation time and on the rules of the available payment methods. When the period ends, the Payer is informed that the link is no longer available.
Can the amount or validity be changed after the link is generated?
The essential details of a link already issued should not be changed. When the amount, validity or other conditions of the operation need to be modified, a new link should be generated.
Why might the intended payment method not appear?
Even where the Client has the payment method contracted with lusopay, if the amount is below the allowed minimum, that payment method automatically becomes unavailable.
Can the link be used more than once?
It depends on the configuration set by the Integrator at generation time. A link can be configured to become unavailable after a payment is completed. The specific conditions should be defined at generation time, where available.
What happens if the Payer doesn't complete the payment?
While the link remains valid and available, the Payer can open it again and try to complete the payment. Whether the operation can be retried may depend on the status of the previous attempt and the method chosen.
Payment methods
Which payment methods can be shown?
Only the methods contracted and configured for the Client that are available for that particular operation are shown. Availability may vary depending on the amount, the currency, the device used and each method's rules.
Can the Client limit which methods are shown?
Yes. Where this option is available, the Client or the Integrator can specify, at generation time, which of the contracted methods should be shown to the Payer.
Why might a payment method not appear?
A method may be unavailable because it is not contracted or active for the Client, because it doesn't apply to the operation's amount or currency, because of device or browser limitations, or because of the provider's own rules.
Why might Apple Pay not be available?
Apple Pay is only shown when the service is active for the Client and the Payer's device, browser and settings meet the method's requirements. The payment page shows information whenever the cause of unavailability can be identified.
Can the link be opened through a QR code?
Yes. The address can be converted into a QR code by the Client or the Integrator, allowing the Payer to open it with their phone's camera. Generating the QR code is external to the link-creation service.
Payment, statuses and confirmation
How does the Payer know if the payment was completed?
At the end of the process, the page shows the result known at that moment. The Client can also send a confirmation through their own channels.
How does the Client know they received the payment?
The Client can check the operation in the Client Area. Where there is an integration, the Client's system can receive notifications and check the operation's status through the technical mechanisms made available.
Is the page shown to the Payer enough to confirm the payment?
No. The Integrator should not rely only on the redirect or the message shown in the browser as final confirmation. The status should be validated through system-to-system notification or a secure query of the operation.
Why might a payment stay pending?
Some methods don't provide final confirmation immediately. The operation may remain pending while awaiting an action from the Payer or confirmation from the bank or the payment method's provider.
Why might a payment be declined?
A decline can result, among other reasons, from incorrect data, insufficient funds, banking limits, incomplete authentication or temporary unavailability. The decision may depend on the bank or the payment method's provider.
What happens if the Payer closes the page during the payment?
The payment should not be considered completed just because the page was closed or because the Payer didn't return to the Client's site. The Client or their Integrator should confirm the status through the mechanisms made available. While the link remains valid, a new attempt may be possible, and the payment page also protects against unwanted duplication.
Security and accessibility
Is Pay by Link secure?
Pay by Link uses secure connections and an encoded payment address to route the Payer to the correct operation. Throughout the flow, validations are applied to protect the integrity of the data and the payment.
What should the Payer check before paying?
The Payer should confirm the page's address, the Client's identification, the amount and the description of the operation. If in doubt, they should contact the Client who sent the link directly.
Is full card data made available to the Client?
No. In card operations, sensitive card data is handled by the providers involved in processing the payment and is not shown to the Client in full.
Does Pay by Link include accessibility features?
Yes. The payment page includes features that let you adapt how content is read and displayed, including options related to text size and legibility, contrast, animations, links and cursor. Exact availability may vary depending on the version in use.
For Integrators
Where can I find the technical integration details?
The endpoints, authentication methods, parameters, codes and request/response examples are available in the technical documentation provided by lusopay. This information should be checked against the version applicable to the environment and the Client.
What information is typically needed to generate a link?
Generation requires identifying the Client and the operation, as well as the essential payment details, such as the order identifier, currency, description and language. Other data may be required or recommended depending on the method and type of operation.
Does the order identifier need to be unique?
Yes. A unique identifier should be used per operation, to allow correct reconciliation where applicable and to reduce the risk of duplication.
How should repeated notifications be handled?
The Integrator should implement idempotent processing. Receiving the same notification more than once should not create duplicate payments, orders or updates.
What should be done when the status isn't conclusive?
The Integrator should keep the operation in a non-final status and use the query mechanism provided before assuming the payment has succeeded or failed.
How can testing be carried out?
Test conditions and data depend on the payment methods and the environment provided. The Integrator should contact lusopay's technical team for the instructions applicable to their project.
How can the payment page be customised?
By checking the manual, the Integrator can customise several aspects of Pay by Link, namely the language, which payment methods to show, sending pre-filled identification fields, forcing a billing form, or even applying link-usage limits, whether by number of opens or by time.