SWIFT MT101 or MT103 Messaging Wire Instructions Sample Clauses

The SWIFT MT101 or MT103 Messaging Wire Instructions clause defines the requirements and procedures for transmitting payment instructions via the SWIFT network using the MT101 or MT103 message formats. This clause typically specifies which party is responsible for initiating the wire transfer, the necessary information to be included in the message (such as beneficiary details and payment references), and any timing or compliance requirements. By standardizing the use of internationally recognized SWIFT message types, the clause ensures secure, efficient, and traceable cross-border payments, reducing the risk of errors or delays in fund transfers.
SWIFT MT101 or MT103 Messaging Wire Instructions. Should you elect in the Specifications to send any electronic wire Orders through an MT101 or MT103 SWIFT message (“Message”), you agree to the following security procedures: • The Message must contain your SWIFT Bank Identifier Code (“BIC”); • The Message must identify (by Account number) the Account to be debited, as stated in the Specifications. • The Message must state a transfer amount that is within the dollar limits (if any) stated in the Specifications. Furthermore, if you select this option, you agree to the following additional terms and conditions: (a) You may, from time to time, amend the Specifications. We shall have a reasonable time to act thereon before accepting it, and are not required to accept any amendment. Additional data or specifications may appear in the Specifications (e.g., Authorized Users), but such additional data or specifications shall not be considered part of the parties’ agreed security procedure and shall not be the basis for you to dispute our good faith or your liability for transactions or actions that are others in accordance with the above security procedures. (b) You agree that any Order or other communication (including an instruction to amend or cancel an Order) issued in your name or BIC that is verified by us pursuant to the above security procedures, and acted upon by us in good faith, shall be effective as your valid, authentic and authorized instruction, fully binding upon you, even if it was in fact not valid, authentic or authorized. You hereby represent and warrant to us that you have determined these security procedures to be commercially reasonable and sufficient for you, according to your expressed wishes and needs, including the size, type and frequency of payment Orders normally issued by you to us. You shall be deemed to renew that representation and warranty each time you send a Message to us. (c) You acknowledge that the above security procedures may offer fewer controls than our standard wire transfer processes of (i) entering wires into Treasury Internet Banking after log-in with Access Credentials, with two person “dual” authorization controls, (ii) telephoning Orders to our central wires department with PIN code verification and two person “dual” authorization controls, and (iii) ordering wires in person at our branches. (d) You acknowledge that this “SWIFT MT101 or MT103 Messaging Wire Instructions” Subsection’s security procedure (i) is not designed or intended to detect errors in content or...
View SourceView Similar (3)

Related to SWIFT MT101 or MT103 Messaging Wire Instructions

  • TEXT MESSAGING WHILE DRIVING In accordance with Executive Order (EO) 13513, “Federal Leadership on Reducing Text Messaging While Driving,” any and all text messaging by Federal employees is banned: a) while driving a Government owned vehicle (GOV) or driving a privately owned vehicle (POV) while on official Government business; or b) using any electronic equipment supplied by the Government when driving any vehicle at any time. All cooperators, their employees, volunteers, and contractors are encouraged to adopt and enforce policies that ban text messaging when driving company owned, leased or rented vehicles, POVs or GOVs when driving while on official Government business or when performing any work for or on behalf of the Government.

  • Reducing Text Messaging While Driving Pursuant to Executive Order 13513, 74 FR 51225 (Oct. 6, 2009), Recipient should encourage its employees, subrecipients, and contractors to adopt and enforce policies that ban text messaging while driving, and Recipient should establish workplace safety policies to decrease accidents caused by distracted drivers.

  • Alerts via Text Message To stop Alerts via text message, text "STOP" to 99785 at anytime. Alerts sent to your primary email address will be unaffected by this action. To restore Alerts on your Mobile Device, just visit the Alerts tab in Online Banking and click the box next to your mobile number for the Alert(s) you would like to receive again. For help with SMS text alerts, text “HELP” to 99785. In case of questions, please contact Customer Care at ▇-▇▇▇-▇▇▇-▇▇▇▇. Our participating carriers include (but are not limited to) AT&T® Wireless, T-Mobile®, U.S. Cellular®, Verizon Wireless.

  • Website, Email Address and Toll-Free Number The Administrator will establish and maintain and use an internet website to post information of interest to Class Members including the date, time and location for the Final Approval Hearing and copies of the Settlement Agreement, Motion for Preliminary Approval, the Preliminary Approval, the Class Notice, the Motion for Final Approval, the Motion for Class Counsel Fees Payment, Class Counsel Litigation Expenses Payment and Class Representative Service Payment, the Final Approval and the Judgment. The Administrator will also maintain and monitor an email address and a toll-free telephone number to receive Class Member calls, faxes and emails.

  • Electronic Visit Verification ("EVV A. To ensure: 1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor; 2. only authorized people access the Contractor's EVV account; 3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim; 4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and 5. service delivery documentation is immediately available for review by HHSC when requested. B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above. C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook. D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable. E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim. F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied. G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook. H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter. I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.