This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
merchant:existing_merchant:selfcare_system:settings:account_updater [2018/05/16 05:06] thiago123 Fixed based on issue #13615 |
merchant:existing_merchant:selfcare_system:settings:account_updater [2022/03/18 11:43] (current) lezlieh edits for secure token |
||
---|---|---|---|
Line 4: | Line 4: | ||
====== Account Updater ====== | ====== Account Updater ====== | ||
- | “Account Updater” refers to secure cards saved on %CompanyName’s system, which have had their Cardholder details updated electronically via “Visa Account Updater” (VAU), and “Mastercard Automatic Billing Updater” (ABU) respectively. This is a process which helps to ensure a smooth automatic billing cycle by minimising payment disruptions due to account changes. | + | “Account Updater” refers to secure tokens saved on Nuvei’s system, which have had their Cardholder details updated electronically via “Visa Account Updater” (VAU), and “Mastercard Automatic Billing Updater” (ABU) respectively. This is a process which helps to ensure a smooth automatic billing cycle by minimising payment disruptions due to account changes. |
Example Use Case: | Example Use Case: | ||
- | * Customers secure card is saved to the gateway. | + | * Customers secure token is saved to the gateway. |
* A monthly subscription is created for the customer. | * A monthly subscription is created for the customer. | ||
* Time passes, and eventually the card expires. | * Time passes, and eventually the card expires. | ||
- | * %CompanyName sends a request to Mastercard or Visa asking for the new card details. | + | * Nuvei sends a request to Mastercard or Visa asking for the new card details. |
- | * Visa/Mastercard sends the updated card details back to %CompanyName. | + | * Visa/Mastercard sends the updated card details back to Nuvei. |
- | * The customers card (secure card) is updated with new info. | + | * The customers card (secure token) is updated with new info. |
* Next months subscription won’t be affected because we now have the correct card details stored for the customer. | * Next months subscription won’t be affected because we now have the correct card details stored for the customer. | ||
Line 25: | Line 25: | ||
* New card number, if it has been changed. | * New card number, if it has been changed. | ||
- | **Secure Card Custom Fields (SCCFs)** | + | **Secure Token Custom Fields (SCCFs)** |
- | At the moment, secure card custom fields are only useful with Account Updater Background Notifications. Because of this, SCCFs are only editable/viewable when Account Updater Background Notifications are Enabled. | + | At the moment, secure token custom fields are only useful with Account Updater Background Notifications. Because of this, SCCFs are only editable/viewable when Account Updater Background Notifications are Enabled. |
**SCCFs Limit** | **SCCFs Limit** | ||
Line 36: | Line 36: | ||
**To create SCCFs on the %Selfcare System** | **To create SCCFs on the %Selfcare System** | ||
- | Once the Secure Card Custom Fields are set, they will be displayed when adding or editing a Secure Card in %Selfcare system. | + | Once the Secure Token Custom Fields are set, they will be displayed when adding or editing a Secure Token in %Selfcare system. |
To know more about how to create custom fields, visit the **[[merchant:existing_merchant:selfcare_system:settings:custom_fields|Custom Fields]]** page. | To know more about how to create custom fields, visit the **[[merchant:existing_merchant:selfcare_system:settings:custom_fields|Custom Fields]]** page. | ||
+ | |||
+ |