• France
status page
Demo shops
assistance
FAQContact support
Search
Categories
Tags
Europe (English)
France
Spain
Europe (English)
India
Homepage
Use cases
Create a payment
Create an installment payment
Create a multi-card (split) payment
Create a payment by Alias (Token)
Create a payment link
Create a recurring payment
Manage subscriptions
Manage your transactions (refund, cancel...)
Analyze your reports
API docs
Embedded Form
REST API
Hosted payment
Mobile payment
File exchange
SDD mandates by REST API
Snippets
Payment methods
Plugins
Marketplace
Guides
Merchant Back Office
Back Office Expert
Functional guides

Create a notification of “SMS sent to the merchant” type

This functionality requires a Lyra SMS account. For more information, see the FAQ.
https://support.lyra.com/hc/fr

  1. Select the type of SMS sent to the merchant notification.
  2. Click Next.
  3. Select one or more trigger events from the list:
    Some events are available only if the corresponding options are enabled.
    Type of event
    Payment accepted

    The rule is triggered when a transaction is created with one of the following statuses: "Waiting for capture", "To be validated", "Captured", "Waiting for authorization", "To be validated and authorized", "Pending".

    		 Payment refused

    The rule is triggered when a transaction is created with the following status:

    "Refused".

    Payment abandoned by the buyer

    The rule is triggered when the Buyer clicks on the "Cancel and return to the shop" button or after expiration of the payment session.

    		 Pending payment waiting for a confirmation of the external platform

    The rule is triggered when a transaction is created with a temporary status .

    Transaction refunded by the merchant

    The rule is triggered when the Merchant performs a refund.

    		 Transaction canceled at the initiative of the merchant

    The rule is triggered when the Merchant performs a refund.

    Transaction declined during the automatic authorization process

    The rule is triggered in case of declined authorization for a differed payment.

    		 Transaction authorized by automatic batch authorization

    The rule is triggered in case of successful authorization for a differed payment.

    Transaction modified by the merchant or the acquirer

    The rule is triggered when the Merchant or the acquirer modifies a transaction.

    		 Transaction validated by the merchant

    The rule is triggered when the Merchant validates a transaction.

    New installment of a recurring payment

    The rule is triggered when creating a new installment of a recurring payment.

    		 Transaction duplicated by the merchant

    The rule is triggered when the Merchant duplicates a refund.

    Token update

    The rule is triggered when payment method details associated to the token are updated.

    		 Token creation

    The rule is triggered when creating a token.

    SEPA direct debit pre-notification.

    The rule is triggered when the pre-notification e-mail is sent to the debtor.

    		 Creation of a recurring payment

    The rule is triggered when creating a new recurring payment.

    Invalid payment form

    The rule is fired as soon as a payment form is detected invalid by the payment gateway.

    		 Regeneration of the key

    The rule is fired as soon as a granted user requests for the regeneration of a new production key.

    Capture sent to the acquirer

    The rule is fired as soon as a capture file is sent to the bank for offsetting.

    		  
  4. Configure the Rule conditions.
    A condition is composed of a variable, a comparison operator and a reference value.
    1. Click the Add button.
    2. Select a variable among the proposed list.
      Variable Description
      Amount (cents) Allows to define a condition based on the amount (in cents).
      Mode (Test or Production) Allows to define a condition based on the mode of soliciting the payment gateway:
      • Test allows to make test payments,
      • Production allows to make real payments
      Payment method Allows to define a condition based on the available payment methods (currencies, technical constraints, etc.) associated with the shop.
      Event source Allows to define a condition based on the origin of the payment:
      • Payment page
      • Notification resent from the Back Office
      • File processing
      • Recurring payment
      • Automatic authorization process
      • Another automatic process
      • Back Office
      • Web Service
      • Payment by IVR
      • Automatic resending of a failed notification
      • REST API
      • Payment order
      • Data collection form
      Installment payment Allows to define a condition based on the type of payment.
      Informative risk assessment Allows to define a condition based on the risk assessment result:
      • Failed
      • Success
    3. Select an operator from the list.
      The suggested operators are specific to the selected variable:
      • equal to
      • less than
      • less than or equal to
      • is on the list
      • different from
      • greater than
      • greater than or equal to
      • is not on the list
    4. Select or enter a value (depending on the selected variable).
      Example:
      During the execution of a rule, the value of a variable is retrieved and compared to the reference value.
      All the conditions must be validated for the rule to be executed.
  5. Click Next.
  6. In the General settings, fill in the fields:
    • Rule reference
    • Phone number to notify
  7. The SMS settings section allows to customize the message.
  8. Click Create.
Jobs
Legal
GDPR
2.93.0-doc-1.11