Important Notice - Credential On File

Update timeline

1. resolved Jul 21, 2018, 04:42 PM UTC

   Summary Recently, Visa and MasterCard announced updates to their requirements for the stored credential transaction framework including mandates to identify initial storage and subsequent usage of payment credentials - commonly known as Credential On File. In compliance with these requirements, the Genesis gateway platform has implemented changes to allow our merchants to provide the relevant information for applicable transactions which will be forwarded to the Card Schemes. These changes are LIVE with the latest Genesis release on July 19. What is the Credential On File Credential On File refers to transactions where the customer's payment credentials (e.g. credit card number) are being stored via Genesis Tokenization service and a transaction is created with the provided token or when the customer credentials are tokenized and stored externally by the merchant. Visa and MasterCard require that any transaction where storing and subsequent usage of the payment credentials occurs, must be flagged as such and its purpose must be provided. Does this change affect me? This affects: - Any merchant who currently stores their customer's payment credentials on their own website, and subsequently uses these credentials in the transaction submitted to the gateway. This includes creating a transaction where the payment credential provided has been saved by the merchant on their own system - Any merchant who currently uses Genesis Tokenization service to store, and subsequently use the customer's payment credentials as part of the transaction. This includes creating a transaction with a token. What do I need to do? For specific scenarios and the list of new parameters required for each, please review the latest Genesis API docs at the Downloads -> API Documentation: https://"your_subdomain".merchant.emerchantpay.net, point 1.26, Credential On File (COF) Implementation details When the merchant uses the Genesis gateway Tokenization service, the gateway will automatically submit the proper credential_on_file flag relating to its initial_customer_initiated and subsequent_customer_initiated values to the Card Schemes, so they are optional for the merchant. The merchant_unscheduled value though needs to be specified and sent by the merchant. When the merchant stores the payment data in its own system, then all the credentials_on_file values are required, including the initial_customer_initiated and subsequent_customer_initiated values which are optional with the gateway-based tokenization only. If you need further assistance or information, do not hesitate to contact us at [email protected] Kind regards, emerchantpay Tech Support team