Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
developer:api_specification:account_updater [2018/12/03 10:26]
127.0.0.1 external edit
developer:api_specification:account_updater [2022/03/21 18:17] (current)
lezlieh update with secure token
Line 4: Line 4:
  
 \\ \\
-"​Account Updater"​ refers to secure ​cards 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 minimizing 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 minimizing payment disruptions due to account changes.
  
 Case example: Case example:
  
-  * Customers secure ​cards are saved to the gateway+  * Customers secure ​tokens ​are saved to the gateway
   * A monthly subscription is created for the customer   * A monthly subscription is created for the customer
   * As time passes, eventually, the cards expire   * As time passes, eventually, the cards expire
   * Nuvei sends a request to Mastercard or Visa asking for the new cards' details   * Nuvei sends a request to Mastercard or Visa asking for the new cards' details
   * Visa/ Mastercard sends the updated card details back to Nuvei   * Visa/ Mastercard sends the updated card details back to Nuvei
-  * The customers'​ cards (secure ​cards) are updated with new info+  * The customers'​ cards (secure ​tokens) are updated with new info
   * Next months subscription won’t be affected because we now have the correct card details stored for the customers.   * Next months subscription won’t be affected because we now have the correct card details stored for the customers.
  
Line 50: Line 50:
   * **Consumes**:​​ text/plain   * **Consumes**:​​ text/plain
  
-The request message size can be modified in a Gateway’s System Settings. The maximum size is 10,000. To ensure messages are not fragmented because of their Secure ​Card Custom Field names; the Secure ​Card custom fields are set as name/value pairs in the CSV string. More specifically,​ they are located under the SCCF1/2/3 columns, and have their names and values delimited by the String "<​AUBN||MSG>"​.+The request message size can be modified in a Gateway’s System Settings. The maximum size is 10,000. To ensure messages are not fragmented because of their Secure ​Token Custom Field names; the Secure ​Token custom fields are set as name/value pairs in the CSV string. More specifically,​ they are located under the SCCF1/2/3 columns, and have their names and values delimited by the String "<​AUBN||MSG>"​.
  
 **The Gateway Sends this request to**: The ​Account Updater Background Notification URL​ set in Terminal Settings. **The Gateway Sends this request to**: The ​Account Updater Background Notification URL​ set in Terminal Settings.
Line 62: Line 62:
 | HASH                    | String ​  | The hash of the current row of data. See **[[developer:​api_specification:​account_updater#​message_hash|Message Hash]]** subsection for more details. ​                                                                          | | HASH                    | String ​  | The hash of the current row of data. See **[[developer:​api_specification:​account_updater#​message_hash|Message Hash]]** subsection for more details. ​                                                                          |
 | CARD TYPE               | String ​  | Card type, e.g. Visa, Mastercard, etc.                                                                                                                          | | CARD TYPE               | String ​  | Card type, e.g. Visa, Mastercard, etc.                                                                                                                          |
-| STATUS ​                 | Integer ​ | Status Code​ of the Secure ​Card Update. See **[[developer:​api_specification:​account_updater#​account_updater_status_codes|Account Updater Status Codes]]** for more details.|+| STATUS ​                 | Integer ​ | Status Code​ of the Secure ​Token Update. See **[[developer:​api_specification:​account_updater#​account_updater_status_codes|Account Updater Status Codes]]** for more details.|
 | CURRENT EXPIRY ​         | String ​  | Card expiry date in the format of "​MMYY"​. ​                                                                                                                      | | CURRENT EXPIRY ​         | String ​  | Card expiry date in the format of "​MMYY"​. ​                                                                                                                      |
-| CARD MODIFICATION DATE  | String ​  | The date the secure ​card was last updated on the gateway via Account Updater. Date format = "​yyyy-MM-dd:​HH:​mm:​ss" ​                        |+| CARD MODIFICATION DATE  | String ​  | The date the secure ​token was last updated on the gateway via Account Updater. Date format = "​yyyy-MM-dd:​HH:​mm:​ss" ​                        |
 | UUID                    | String ​  | Unique ID to validate message authenticity ​                                                                                                                     | | UUID                    | String ​  | Unique ID to validate message authenticity ​                                                                                                                     |
 | MSG EXPIRES IN          | Numeric ​ | Milliseconds. When the gateway will stop accepting merchant responses for this request. ​                                                                        | | MSG EXPIRES IN          | Numeric ​ | Milliseconds. When the gateway will stop accepting merchant responses for this request. ​                                                                        |
-| SCCF1                   | String ​  | Any secure ​card custom fields will go here. The string will contain both name and value of the secure ​card custom field. For more information see **ND001** below  |+| SCCF1                   | String ​  | Any secure ​token custom fields will go here. The string will contain both name and value of the secure ​token custom field. For more information see **ND001** below  |
 | SCCF2                   | String ​  | Same as SCCF1 | | SCCF2                   | String ​  | Same as SCCF1 |
 | SCCF3                   | String ​  | Same as SCCF1 | | SCCF3                   | String ​  | Same as SCCF1 |
Line 156: Line 156:
 ==== Account Updater Status Codes ==== ==== Account Updater Status Codes ====
  
-The message from the gateway contains a field called “STATUS”. This field reflects the gateways Secure ​Card account updater status. This means that the gateway has sent this secure ​card to Mastercard/​Visa (ABU/VAU) and received an update status from their service.+The message from the gateway contains a field called “STATUS”. This field reflects the gateways Secure ​Token account updater status. This means that the gateway has sent this secure ​token to Mastercard/​Visa (ABU/VAU) and received an update status from their service.
  
 The following table details the meaning of each status code. The following table details the meaning of each status code.
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International