Differences
This shows you the differences between two versions of the page.
| Next revision Both sides next revision | |||
|
merchant:existing_merchant:selfcare_system:settings:enhanced_data_templates [2019/05/23 16:04] hanv created |
merchant:existing_merchant:selfcare_system:settings:enhanced_data_templates [2019/05/23 16:22] hanv |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| * **Platform default template**: your gateway might already have a default pre-defined template. You can see this template in your list (as above), but you can't change or deactivate this template. This template is going to be the base for the autofill feature. | * **Platform default template**: your gateway might already have a default pre-defined template. You can see this template in your list (as above), but you can't change or deactivate this template. This template is going to be the base for the autofill feature. | ||
| + | * **The autofill feature**: when your terminal is configured without autofill, every transaction received by any channel (VT, Open Batch or Integrations) is going to receive the "default template"'s data where you didn't inform anything. So say you sent a transaction without any enhanced data field and the terminal used has autofill enabled. In this case, the gateway is going to use the default template's data (the platform's or yours, if you defined one for the terminal) to complete the missing data. | ||
| + | * **Terminal templates**: besides the platform default template (if existing), you can also define templates for terminals. If you define templates, they are going to be available whenever you decide to send or add enhanced data to a transaction. Also, you can define one of your terminal's templates as the default one for that terminal - in this case, the payment gateway is going to use the autofill with this template, instead of using the platform one. | ||