MoTo payments
Paylands offers a feature called "Pagos Mo/To" to process offline payments. Mo/To is the acronym for Mail Order / Telephone Order.
With this web tool, you will be able to upload a CSV file containing payment orders to be sent by mail or SMS to users.
The user will receive in his email/phone a link that will take him to the payment page from where he will be able to finalize the payment.
The tool supports specific templates to be sent by SMS or e-mail. To use a customized template, please send an e-mail to soporte@paylands.com.
Structure of the payment file.
MoTo payments are indicated by means of a CSV, which is a text document in which the first line contains the header and the rest of the lines the data of each payment.
| Header | Type | Required | Description |
|---|---|---|---|
| AMOUNT | Integer | YES | Amount to collect, in cents. |
| OPERATIVE | String | YES | Type of operation to be performed. It can be AUTHORIZATION or DEFERRED. For a payment, the AUTHORIZATION value must be sent. |
| DESTINATION | String | YES | Email/phone of the user who will receive the link to make the payment. In the case of telephone, it must be indicated in international format, indicating the country code. |
| SECURE | String | YES | true/false. Indicates whether the payment will be secure or not. |
| CUSTOMER_EXT_ID | String | NO | Identifier of the user who will make the payment. |
| SOURCE_UUID | String | NO | UUID of the card associated to the customer_ext_id making the payment. |
| ADDITIONAL | String | NO | Free text field to be sent to the merchant in the notification. |
| URL_POST | String | NO | URL of the merchant where the notification with the payment result will be sent to. |
| URL_OK | String | NO | URL of the merchant where the user will be redirected if the payment was successful. |
| URL_KO | String | NO | URL of the merchant where the user will be redirected if the payment failed. |
| CARD_TEMPLATE | String | NO | Code that identifies the template to be used to enter the card data. |
| MOTO_TEMPLATE | String | NO | Code that identifies the template that will be used to send the email/SMS. |
| DCC_TEMPLATE | String | NO | Code that identifies the template to be used in case the payment has DCC. |
| CERTIFIED | String | NO | true/false. Indicates if the email or sms sending will be certified. |
| EXTRA_DATA | String | NO | extra_data fields separated by semicolon (;). Subkeys will be joined using a dot (.). For example, sending the cof=RECURRING would be sent as cof.reason:RECURRING |
| ROUTE | String | NO | If the delivery method is PHONE, it determines the routing of the SMS. It can be DIRECT or INDIRECT. The default will be DIRECT. |
Values are delimited with a comma: ",". Optional headers containing no value can be omitted. Null or empty values are indicated by leaving a gap between commas. An example of a CSV is as follows:
AMOUNT,OPERATIVE,DESTINATION,SECURE,SOURCE_UUID,CUSTOMER_EXT_ID,ADDITIONAL,URL_POST,URL_OK,URL_KO,CARD_TEMPLATE,MOTO_TEMPLATE,DCC_TEMPLATE,CERTIFIED
12035,AUTHORIZATION,+34666554411,false,,user_1234,additional_info_1234,http://google.es/notification,http://google.es/ok_payment,http://google.es/ko_payment,,90895BE4-F614-447A-AE7F-082B248FE3A3,,false
In the example, the order will be created for a non-secure payment of 120.35€, associated to the customer 'user_1234'. The value of the 'SOURCE_UUID' field is NULL because no value has been specified.
Tokenized MoTo payments
If the card has been tokenized previously you can indicate the SOURCE_UUID of the card and the CUSTOMER_EXT_ID to which the card was associated so that the payment is carried out directly through the 3DS, without the user having to indicate the card data on the payment card. Tokenized payments are SECURE regardless of whether the secure field is set to TRUE or not.
Custom fields in email and SMS templates
Custom fields can be included in the email and SMS templates. To do so, the format to be sent, either from the panel form or by sending them via API must be:
key1:value1;key2:value2
The different fields must be separated by semicolons.
For example, sending in the motorcycle campaign, in the additional field the following value:
name: Juan García; age: 28
In the email/sms template these values can be accessed as follows:
Welcome {{customFields.name}},
happy {{customFields.age}} years.