Link Payment

Payment links offer a fast and secure way to collect payments from your customers without requiring a full website or custom integration. These links can be shared directly with customers and allow them to ay securely through a pre-defined checkout page using their preferred payment method.

Create a Link Payment

To generate a new payment link, follow these steps within the Localpayment Panel:

Go to: PayIn > Checkout > Link Payment

Destination Account

When creating a payment link, you need to specify the Destination Account where the funds will be received. You have two convenient options for setting this up:

1. Select a Saved Favorite: Choose from a list of previously saved account configurations. This option is ideal for recurring products or services. Note: The list of saved favorites only appears when you have existing configurations. For example, it won't be displayed the first time you create a link payment.

2. Enter Details Manually: Provide the necessary information for a new payment link:

   • Product/Service Title: A clear title for what the payment is for.

   • Country: Select the country where the payment will be processed.

   • Destination Account: Choose the specific account to receive the funds.

Click Next to proceed with payment link setup.

How Favorites Work

Favorites streamline the process of creating payment links for frequently used configurations.

If you select a saved favorite, the payment link creation form will be pre-populated with the saved settings, including:

• Payment amount

• Product/Service Title

• Description

• Country

• Destination Account

You can either accept the pre-loaded configuration or make modifications as needed for that specific link.

When a favorite is selected, a Generate Direct Link button will appear, allowing you to instantly create and share the payment link.

Link Payment Configuration

To configure a payment link, the necessary product or service information must be provided. This includes the transaction currency, the total amount, and an optional reference identifier to help identify or track the transaction.

Basic Configuration

The currency must be selected based on the payment context. The amount represents the total to be charged, and an optional identifier can be added for internal reference or reporting purposes.

Add Detailed Items

For more granular configuration, the "Add detailed items" option allows additional information to be included for each product or service.

There are two options available:

• Selecting from a list of existing products previously saved in the catalog.

• Creating a new product using the "Add another product" option.

When creating a new product, the following attributes must be defined:

• Title of the product or service.

• Product code to uniquely identify the item.

• Category that best classifies the item.

• Description to provide additional context or usage details.

• Unit price, representing the cost per item or service unit.

• Quantity, indicating how many items are included in the payment.

Multiple items can be added to a single payment link if needed, and each one will be displayed as part of the payment details.

Once all required fields and optional product details are configured, click the Submit button to generate the payment link.

Sharing the Link Payment

Once you click the Submit button to create the payment link, a new window will display the generated link. In this window, you also have the option to save the current configuration as a favorite, allowing you to quickly generate similar links in the future.

If you modify a pre-loaded favorite's settings, the button will change to "Save modifications". Clicking this will save your adjustments, ensuring that all new links created from that favorite reflect the updated configuration.

Here's an example of a generated payment link:

https://web-checkout.stage.localpayment.com/5605b8badc3f4d2283173d3fcff4c613

Once generated, your payment link can be effortlessly shared with your customers via email, messaging apps, social media, or any other preferred communication channel.

When the customer clicks the link, they’ll see all available payment options (such as credit/debit card, cash, or bank transfer) and can complete the payment directly from the interface.

Once the payment is successfully completed, Localpayment will send a webhook to your application with the updated transaction status.

Webhook Example

Here’s an example of a webhook sent after a successful credit card payment via a payment link:

{
  "transactionType": "PayIn",
  "transactionFlow": null,
  "country": "MEX",
  "data": {
    "transactionType": "PayIn",
    "externalId": "a533028d-d605-410c-afc5-55b10ea8d",
    "internalId": "b301067a-ccc8-46c2-b879-6feb38985b9c",
    "paymentMethod": {
      "type": "CreditCard",
      "code": "1600",
      "flow": "DIRECT"
    },
    "country": "MEX",
    "currency": "MXN",
    "amount": 899.0,
    "accountNumber": "48x.xxx.xxxxxx58",
    "confirmed": {
      "currency": "MXN",
      "fxQuote": 1.0,
      "amount": 899.0
    },
    "payment": {
      "currency": "MXN",
      "fxQuote": 1.0,
      "financingFee": 0.0,
      "amount": 899.0
    },
    "localTaxes": [],
    "withHoldings": [],
    "fees": {
      "description": "Fee",
      "currency": "MXN",
      "fxSource": 18.91123106,
      "fxQuote": 19.85679262,
      "amount": 29.79,
      "account": "48x.xxx.xxxxxx58"
    },
    "status": {
      "code": "200",
      "description": "COMPLETED",
      "detail": "The payin was credited"
    },
    "merchant": {
      "type": "COMPANY",
      "name": "LocalPayment"
    },
    "payer": {
      "type": "INDIVIDUAL",
      "name": "John",
      "lastName": "Doe",
      "document": {
        "type": "RFC",
        "id": "XXXXXXXXXXXX"
      },
      "email": "[email protected]",
      "phone": {
        "countryCode": "us",
        "areaCode": "1",
        "number": "9012345678"
      },
      "address": {
        "street": "",
        "city": "",
        "state": "",
        "country": ""
      }
    },
    "intermediaries": [],
    "date": {
      "creationDate": "2025-06-13T16:06:02Z",
      "processedDate": "2025-06-13T16:06:05Z"
    },
    "card": {
      "token": "6Ncj4ffe1GlIlCx1AWkuoiTcJjBhzrk/EDbWUHUaBMw=",
      "bin": "424242",
      "brand": "VISA",
      "country": "GB",
      "name": "john doe",
      "last4": "4242",
      "expirationYear": 2029,
      "expirationMonth": 11,
      "installments": 1
    },
    "errors": []
  }
}

Our Dynamic tutorial: