ID/Password Requirements Sample Clauses

ID/Password Requirements. Customer point of contact Authentication of a either a Customer of Fund point of contact (“Point of Contact”) in the Distribution Support Services Web Site is based on an Operator ID and Password. Required – The Operator ID, chosen by Customer or the applicable Fund, shall have access as determined by Customer or such Fund, as applicable. Access will be specific to the management company associated with the Fund. This may include the following access levels, at Customer’s or the applicable Fund’s option, inquiry only access (Point of Contact may only view information related to Users) or update access (Point of Contact may update profiles related to Users, including, but not limited to, changing, adding and deleting User information). DST shall store the Operator ID and associated access levels. Any personnel changes or access changes affecting Point of Contact must be communicated to DST promptly. Required – Password is used in conjunction with Operator ID to access the Distribution Support Services Web Site, which consequently provides access to any User information (profile, firm, address, authorization information, etc.).
Sample 1Sample 2Sample 3See All (37)
AutoNDA by SimpleDocs
ID/Password Requirements. Initial authentication of a shareholder in FAN Web is accomplished with account number and Social Security Number (SSN) and is used to issue a personal identification number (PIN) to the shareholder. Thereafter, shareholder authentication may be accomplished by any of the three following methods, determined by the FAN Web options selected by the Trust: Method One Required – Account number is used as the identification (ID) of the shareholder. Required – The PIN is used as the access to the entered account. Optional Requirement – Social Security Number (SSN) may be chosen as an additional required field by the Trust, as part of the FAN Web options, to add another level of authentication to access the entered account number. Method Two Required – Social Security Number (SSN) of the shareholder.
Sample 1Sample 2Sample 3See All (30)
ID/Password Requirements. Initial authentication of a shareholder in the Shareholder Portal is accomplished with account number and Social Security Number (SSN) and is used to issue a personal identification number (PIN) to the shareholder. Thereafter, shareholder authentication may be accomplished by any of the three following methods, determined by the Shareholder Portal options selected by the Trusts: Method One Required – Account number is used as the identification (ID) of the shareholder. Required – The PIN is used as the access to the entered account. Optional Requirement – Social Security Number (SSN) may be chosen as an additional required field by the Trusts, as part of the Shareholder Portal options, to add another level of authentication to access the entered account number. Method Two Required – Social Security Number (SSN) of the shareholder.
Sample 1Sample 2
ID/Password Requirements. Users Authentication of a User in Vision is based on the Vision Operator ID and Password. Required – The Vision Operator ID, assigned by SS&C, shall have access authorization as determined by Customer. This may include the following access levels, at Customer’s option, the contents of which shall be determined by Customer: Unrestricted Access – This allows the User to view any account information for all of Customer’s Financial Products. Dealer Level Access – This allows the User to view any account information with the authorized dealer number. Dealer/Branch Level Access – This allows the User to view any account information with the authorized dealer and branch combination. Dealer/Representative Level Access – This allows the User to view any account information with the authorized dealer and representative combination. Tax ID Level Access – This allows the User to view any account with the authorized Social Security Number and/or TIN of the Unit Holder. Trust/TPA Access – This allows the User to view any account with the authorized trust company or Third Party Administrator number assigned to the underlying account/contract. Required – Password is used in conjunction with Vision Operator ID to access the Vision Web Site, which consequently provides access to any Financial Product account information that has been previously authorized by Customer. Vision does not use a personal identification number (PIN).
Sample 1
ID/Password Requirements. DST will establish a single Recipient ID and Password for each Recipient and will permit access to the Files residing on the DST Web Site associated with the given Recipient ID and Password without further inquiry. Each Recipient’s Password will be encrypted.
Sample 1
ID/Password Requirements. Customer Point of Contact DST will establish a single Operator ID and Password for use by the Customer point of contact to access the Distribution Support Services Web Site. Required—The Operator ID shall have access as determined by the Customer. Access will be specific to the management company associated with the Customer. This may include the following access levels, at Customer’s option, inquiry only access (Customer point of contact may only view information related to Recipients) or update access (Customer point of contact may update profiles related to Recipients, including, but not limited to, changing, adding and deleting Recipient information). DST shall store the Operator ID and associated access levels. Any personnel changes or access changes affecting the Customer point of contact must be communicated to DST promptly. Required—Password is used in conjunction with Operator ID to access the Distribution Support Services Web Site, which consequently provides access to any Recipient information (profile, firm, address, authorization information, etc.) Annex 1
Sample 1

Related to ID/Password Requirements

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Testing Requirements 12.1. Workplaces -

  • Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. Item Not Received additional requirements To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.

  • Rule 144 Requirements After the earliest of (i) the closing of the sale of securities of the Company pursuant to a Registration Statement, (ii) the registration by the Company of a class of securities under Section 12 of the Exchange Act, or (iii) the issuance by the Company of an offering circular pursuant to Regulation A under the Securities Act, the Company agrees to:

  • Screening Requirements Xxxxxx shall ensure that all prospective and current Covered Persons are not Ineligible Persons, by implementing the following screening requirements.

  • W-9 Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a properly completed Internal Revenue Service (“IRS”) Form W-9. The purpose of the W-9 form is to document the SS# or FEIN# per the IRS. Note: W-9s submitted for any other entity name other than the Grantee’s will not be accepted.

  • Data Requirements ‌ • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.

  • E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.

  • TITLE VI REQUIREMENTS H-GAC in accordance with the provisions of Title VI of the Civil Rights Act of 1964 (78 Xxxx. 000, 00 X.X.X. §§ 0000x to 2000d-4) and the Regulations, hereby notifies all bidders that it will affirmatively ensure that any disadvantaged business enterprises will be afforded full and fair opportunity to submit in response to this Agreement and will not be discriminated against on the grounds of race, color, or national origin in consideration for an award.

Time is Money Join Law Insider Premium to draft better contracts faster.