History Processing File Sample Clauses

History Processing File. This file is generated from the experiences of the Household Companies. It consists of RAL payment history for the last four (4) years and current bad debt. This data is used for scoring a potential Instant RAL customer, is coded, and resides in the Instant RAL decision module incorporated into the TPS software. Block Services is prohibited from accessing and decoding such software, except in response to, and to fulfill, a consumer's request for a RAL. Block Services shall not use this file for any other purpose, including but not limited to marketing its products.
View Source
History Processing File. This file is generated from the experiences of the Household Companies. It consists of RAL payment history for the last four (4) years and current
View Source

Related to History Processing File

  • Complete Servicing File All documents comprising the Servicing File will be or have been delivered to the Master Servicer with respect to each Mortgage Loan by the deadlines set forth in the Pooling and Servicing Agreement and/or this Agreement.

  • Database File The Servicer will provide the Successor Servicer with a data file (in a format reasonably acceptable to the Indenture Trustee and the Servicer) containing the database file for each Contract (i) as of the Cutoff Date, (ii) thereafter, as of the last day of the preceding Due Period on each Determination Date prior to a Servicing Transfer, and (iii) on and as of the Business Day before the actual commencement of servicing functions by the Successor Servicer following the occurrence of a Servicing Transfer.

  • Processing of Deposit files The use of compression is recommended in order to reduce electronic data transfer times, and storage capacity requirements. Data encryption will be used to ensure the privacy of registry escrow data. Files processed for compression and encryption will be in the binary OpenPGP format as per OpenPGP Message Format -­‐ RFC 4880, see Part A, Section 9, reference 3 of this Specification. Acceptable algorithms for Public-­‐key cryptography, Symmetric-­‐key cryptography, Hash and Compression are those enumerated in ▇▇▇ ▇▇▇▇, not marked as deprecated in OpenPGP IANA Registry, see Part A, Section 9, reference 4 of this Specification, that are also royalty-­‐free. The process to follow for the data file in original text format is: (1) The XML file of the deposit as described in Part A, Section 9, reference 1 of this Specification must be named as the containing file as specified in Section 5 but with the extension xml. (2) The data file(s) are aggregated in a tarball file named the same as (1) but with extension tar. (3) A compressed and encrypted OpenPGP Message is created using the tarball file as sole input. The suggested algorithm for compression is ZIP as per ▇▇▇ ▇▇▇▇. The compressed data will be encrypted using the escrow agent’s public key. The suggested algorithms for Public-­‐key encryption are Elgamal and RSA as per ▇▇▇ ▇▇▇▇. The suggested algorithms for Symmetric-­‐key encryption are TripleDES, AES128 and CAST5 as per ▇▇▇ ▇▇▇▇. (4) The file may be split as necessary if, once compressed and encrypted, it is larger than the file size limit agreed with the escrow agent. Every part of a split file, or the whole file if not split, will be called a processed file in this section. (5) A digital signature file will be generated for every processed file using the Registry Operator’s private key. The digital signature file will be in binary OpenPGP format as per RFC 4880 Section 9, reference 3, and will not be compressed or encrypted. The suggested algorithms for Digital signatures are DSA and RSA as per ▇▇▇ ▇▇▇▇. The suggested algorithm for Hashes in Digital signatures is SHA256. (6) The processed files and digital signature files will then be transferred to the Escrow Agent through secure electronic mechanisms, such as, SFTP, SCP, HTTPS file upload, etc. as agreed between the Escrow Agent and the Registry Operator. Non-­‐electronic delivery through a physical medium such as CD-­‐ROMs, DVD-­‐ROMs, or USB storage devices may be used if authorized by ICANN. (7) The Escrow Agent will then validate every (processed) transferred data file using the procedure described in Part A, Section 8 of this Specification.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet