Integration Guidelines
Version and Authorization
Version
Explanation of change / updates
Date of Updates
Effective Date of Implementation
1.0
Description of integration guidelines
Dec 13, 2023
Dec 13, 2023
Acronyms/Definitions
The Company
Machnet Technologies, Inc.
FI Partner
FI Partner means financial institution partners of the Company which enable the Company to offer the Program
Application
Application means a website and/or mobile app developed utilizing the Platform with the intent of providing the Services to users.
Overview
The Program provides depository and other payment services (“Services”) to users in association with its FI Partners. These services need to comply with Federal and State regulations pertaining to money service and payment businesses in addition to the policies and guidelines specified by the FI Partners. The services should at all times, provide accurate information to users utilizing the service regarding the nature of the program, the service providers involved and all information that is pertinent to users with respect to their registration for the service, the account maintained by them and transactions conducted by them.
The purpose of this document is to describe the guidelines that need to be complied by all Applications catering to users utilizing the Program. This document specifies the requirements that Applications shall be required to follow in order to ensure that they:
are compliant with federal regulations and policies specified by FI Partners,
safeguard the privacy and interests of the users, and
ensure transparency regarding the parties involved in the service and the transactions conducted by them using the Service.
The guidelines prescribed in this document are subject to change at the discretion of the Company with or without prior notice. Any such change shall be effective from the date such changes are communicated to the Application.
Transaction Requirements
This section describes the guidelines that need to be complied by the Application when a user creates any transaction. For the purpose of this document, a transaction is any event initiated by a user which involves the movement of funds from one point to another.
Transaction Confirmation Page
The Application should display a confirmation page to the user before the user submits any transaction. The purpose of the page is to provide an opportunity for the user to ensure that all information for the transaction is accurate.
The confirmation page should provide the following information for the user to view and confirm:
Transaction Details:
Transaction Amount (in USD)
Transaction Fee
Total Amount debited for the transaction
Exchange Rate
Currency and Amount to be received by the recipient
Transaction Recipient Detail
Name of Recipient
Method of Payment
Details of Payment
ACH/Wire: Bank Name, Account Number
Money Transfer:
Cash Pick-up: Pickup location, PIN Number
Wallet: Wallet Network, Wallet ID
Bank Deposit: Bank Name, Account Number
The user should be able to proceed forward with the transaction or edit the transaction details after viewing the confirmation page.
In the case of recurring transactions, the Application should include the following text on the confirmation page:
To cancel this transaction, Click Here. This is an authorized recurring debit from the designated payment method. If you would like to cancel future payments, please email us at <Application email address> with at least 3 business days’ notice.
The Click Here in the text above should have a link to the section in the Application from where the user can cancel the recurring transaction.
Debit Authorization Text
After the confirmation page and prior to submission of a transaction, the Application should display the following message box to the user requiring the user to confirm authorization to debit the specified payment method for the amount of the transaction. The authorization text will be defined based on the payment methods used as the processors are different. Please find the verbiages as follows:
For ACH Transactions
Stand Alone Transaction
I authorize Machnet Technologies Inc (“Machnet”) via <<Name of Application>> to debit the account/card indicated in this form for the noted amount on today's date. I will not dispute Machnet debiting my checking/savings account, so long as the transaction corresponds to the terms indicated in this web form. (Note: The funds for your transaction will be debited from your account by Machnet via Global Innovations Bank). Click here for details.
Click Yes to continue or click Cancel
Please note that “Click Here” in the above message should provide a link to Machnet’s User Agreement.
Recurring Transaction
I authorize Machnet Technologies Inc. (“Machnet”) via <<Application Name>> to debit the account/card indicated for the recurring transactions according to the form and my agreement with <<Application Name>>. I will not dispute so long as the transactions correspond to such terms. This payment authorization is valid and will remain effective unless I cancel this authorization by emailing <<Application Name>> at <<Application Email Address>> at least 3 business days in advance. (Note: The funds for your transaction will be debited from your account/card by Machnet via Global Innovations Bank). Click here for details.).
Click Yes to continue or click Cancel
Please note that “Click Here” in the above message should provide a link to Machnet’s User Agreement.
For Card Transactions
Stand Alone Transaction
I authorize Machnet Technologies Inc (“Machnet”) via <<Name of Application>> to debit the account/card indicated in this form for the noted amount on today's date. I will not dispute Machnet debiting my checking/savings account, so long as the transaction corresponds to the terms indicated in this form. (Note: The funds for your transaction will be debited from your account by Machnet via Tabapay Inc.). Click here for details.
Click Yes to continue or click Cancel
Please note that “Click Here” in the above message should provide a link to Machnet’s User Agreement.
Recurring Transaction
I authorize Machnet Technologies Inc. (“Machnet”) via <<Application Name>> to debit the account/card indicated for the recurring transactions according to the form and my agreement with <<Application Name>>. I will not dispute so long as the transactions correspond to such terms. This payment authorization is valid and will remain effective unless I cancel this authorization by emailing <<Application Name>> at <<Application Email Address>> at least 3 business days in advance. (Note: The funds for your transaction will be debited from your account/card by Machnet via Tabapay Inc.). Click here for details.).
Click Yes to continue or click Cancel
Please note that “Click Here” in the above message should provide a link to Machnet’s User Agreement.
2FA Verification
Prior to confirmation of a transaction, the Application should conduct a 2FA verification to ensure that the user is actually conducting the transaction and it is not a case of account theft. The 2FA verification could be conducted by means of an OTP sent to the user’s registered phone number, email address, or any other authentication services feasible to the Application.
Transaction Receipt
The receipts for transactions initiated by users will be generated by Machnet. The Application shall ensure necessary integration with Machnet in order to obtain receipts for user transactions. The Application should follow the following guidelines regarding the transaction receipt:
The receipt shall be provided to the user via email.
The user should also be able to download the receipt from the email.
The user should also be able to view and/or download the receipt from the user dashboard.
Transaction Cancellation and Refund
The Application should allow the user to cancel any transaction until it has been forwarded for processing. The Application should provide an adequate process in the application, whether or not in the user dashboard, to cancel a transaction.
If the user is unable to cancel a transaction by themselves, the user should be guided to the customer support team of the Application to request for a cancellation. To the extent possible, the Application should endeavor to cancel the mentioned transaction. Please note that a transaction that has been batched for processing may not be canceled. In such cases, the Application should enable the user to request for a refund for the transaction. In such cases, the user should be provided the following message:
This transaction cannot be canceled at the moment. If you still want to proceed with the cancellation, please contact customer support by phone(..............) or email at ………………………………….”
In case of a money transfer transaction, the user should be able to cancel the transaction for up to 30 minutes from the time of submission of the transaction in case the transaction is not processed or paid out. The user should be provided the following message:
You can cancel for a full refund within 30 minutes of payment unless the funds have been forwarded for processing or payout.
Email and Mobile Number Verification
In order to improve user security and minimize the risk of fraudulent users in the Application, it is a mandatory requirement for the Application to implement an email verification process and mobile verification process during the user registration process. This will assist in filtering fraudulent users and mitigate the risk of fraudulent transactions in the Application.
Email Notifications
The Application should provide email notifications to users at various events and stages of user on-boarding and transaction process. At a minimum, the Application should provide email notifications as follows:
Event Type
Notification Trigger/Timeline
Content Requirement
Account Creation / Registration
After the user has been registered in Machnet
Welcome email
TOS and PP (Hosted by Machnet) links for referral.
Client’s customer support details
Account Verified
After the user has been verified.
Include the following verbiage:
“You have been successfully verified. Pursuant to the User Agreement, we have set up a Deposit Account for you with our banking service provider, Global Innovations Bank, member FDIC. Please Click Here to view the User Agreement and Privacy Policy.”
Client’s customer support details
Disclaimer for the service
KYC related emails (Document requested / Retry requested)
If a user has a KYC status other than verified
User’s verification status
If applicable, next steps that the user should take to resolve the issue
Client’s customer support contact info
Disclaimer for the service along with the links for TOS and PP (Hosted by Machnet)
Transaction Creation
After the transaction is created by user
In case of cash pickup transactions, once the fund is ready to be collected by the recipient.
Transaction reference number
Client’s customer support contact info
Copy of transaction receipt
Disclaimer for the service along with the links for TOS and PP (Hosted by Machnet)
Transaction created for recurring transaction
Before a new transaction is created if part of recurring transactions
Transaction reference number
Client’s customer support contact info
Copy of transaction receipt
Disclaimer for the service along with the links for TOS and PP (Hosted by Machnet)
Ongoing KYC
Every six months after the user has been created and verified
Request the user to update their KYC details if there are any changes.
If a user selects Yes for any changes, they should be guided to their user dashboard. (a link can be given to redirect to their user profile or to login to the account.)
If a user selects No for the changes, no action is required.
The log of the responses should be maintained
Disclaimer for the service along with the links for TOS and PP (Hosted by Machnet)
Account Statement
Within three (3) business days from the end of each calendar month
Copy of Statement in PDF format
Changes to Scheduled Transaction(s)
In advance of any changes to a scheduled transaction(s) amount, frequency or timing.
Details of change in the scheduled transaction(s).
Transaction Payout (Applicable for money transfer transaction)
Transaction is paid out
If Bank Deposit, last 4 digits of the recipient bank account number
If Mobile Wallet, last 4 digits of the mobile wallet ID
Transaction is ready for cash pickup
In case of cash pickup, once the fund is ready to be collected by the recipient.
Transaction reference number
Client’s customer support details
Copy of transaction receipt
Details that need to be presented by the recipient to collect a cash pickup transaction i.e., ID Card, Branch Name, PIN Number, etc.
Disclaimer for the service along with the links for TOS and PP (Hosted by Machnet)
Delete Account Request Initiated
After the user clicks on the Delete account option from the service platform
Information that we have received an account deletion request, and we are in the process of completing the account deletion and thus all the services for the user is freezed at the moment.
Client’s customer support
Disclaimer for the service
Delete Account Request COmpleted
After the deletion of the account is completed
Information that the account deletion process has been completed.
Client’s customer support
Disclaimer for the service
User Dashboard
The Application should provide an interface to the user after the registration process which, at minimum, provides the following capabilities to the user:
View the details of all transactions initiated by the user, including detailed breakdown showing processing status and timeline for account funding, withdrawal and transfer components of user transactions.
View and download transaction receipt
Cancel transactions initiated by the user
View and download their account statement
View the information/documents provided by the user as part of their KYC
Edit and/or update their KYC information/documents
View the current tier level of the user and the available transaction limits
Account Statements
The Application should provide account statements to the user at the end of every calendar month showing the incoming and outgoing transactions as well as the balance available in their account (wherever applicable) as on the reporting date. The format for the statement can be found in the link here.
User Agreement and Privacy Policy
Service User Agreement and Privacy Policy
The Service User Agreement and Privacy Policy are agreements that a user needs to accept during registration in the Application. The User Agreement specifies the terms and conditions based on which the user may utilize the Services. Similarly, the Privacy policy contains details on the information collected by the Application from the user and how it will utilize such data during the course of the usage of Services by the user.
The Service User Agreement and Privacy Policy shall be hosted by the Company, and the Application shall be required to display them and/or provide access to users of such agreements in locations and events as described hereinbelow.
Placement
a. Landing Page
The User Agreement and Privacy Policy shall be placed on the website's Landing Page. In the case of a mobile app, the agreements shall be placed on the menu bar/section
b. User Registration
The Application should display the User Agreement and Privacy and this should be clearly visible/accessible to the users during the sign-up process of the Application such that the users have ample opportunity to refer to the Agreements before they register for the Services. Additionally, users shall be required to accept the User Agreement and Privacy Policy at the time of registration for the Services.
c. Email Notification
The Application should place the Service User Agreement and Privacy Policy in all the transaction related and user registration email notifications.
Application Specific User Agreement
In addition to the Service User Agreement and Privacy Policy, the Application may also have its own user agreement, which governs the user’s utilization of the Application. The Application may include such agreements on the landing page along with the Service User Agreement and Privacy Policy; however, the Application shall ensure that the Service User Agreement and Privacy Policy are distinctly visible on the Landing Page.
Further, any such application specific user agreement should include the following clause pertaining to the payment services provided by the Application:
Terms pertaining to Payment Services
The payment services provided by <<Application Name>> are enabled by Machnet. All terms and conditions pertaining to such payment services shall be governed by Machnet’s User Agreement and Privacy Policy. Please Click Here to view the User Agreement and Click Here to view the Privacy Policy.
If the Application provides other products or services in addition to the Services, the Application may include the product related agreements in the landing page; however, due care should be taken to ensure that the Service User Agreements and Privacy Policy are distinctly visible.
Disclaimer
Content
In the interest of transparency regarding the provider of the service, the Application should display the following disclaimer at various locations in the Application.
This service is enabled by Machnet Technologies Inc (“Machnet”). Machnet is a financial technology company, not a bank. The Banking Services are provided by Global Innovations Bank, member FDIC.
Placement
The Application should place the disclaimer in the following locations:
Landing page of the Application
Footer section of each page of the Application (menu bar in case of mobile app)
Transaction receipt
Email notification
User registration page
Contact Us Page
Content
The Application should have a Contact Us section which provides information regarding the modes through which users can contact the application. The Section shall, at minimum, include the following details:
Phone no. or email address
Address
Operating hours
Details of Error Resolution Steps (Refer Section Error Resolution)
Placement
Landing Page of the Application
User Dashboard (Footer section/menu bar)
Error Resolution
Content
The Application should provide clear information as to the steps users are required to follow in order to report and seek resolution for any error or grievances they may have while utilizing the Services.
The error resolution process should clearly provide the following information, at minimum, to users to report their grievances:
Phone no. or email address of the client’s customer support team
Address of the support team
Operating hours of the support team
The error resolution process should also provide the following escalation information:
In case your grievances are not addressed by the <<Application Name>> or for any escalation purposes, please contact Machnet at its Email Address: [email protected].
This service is enabled by Machnet Technologies Inc (“Machnet”). Machnet is a financial technology company, not a bank. The Banking Services are provided by Global Innovations Bank, member FDIC. If you have any grievances, you can report to Global Innovations Bank at ……………@gib.com
Placement
Contact Us section
Transaction Receipt
Email notification
User Account Deletion
Users have the right to delete their accounts if they choose to stop using the services and want their account information to be deleted from the service platform as per the privacy act. Hence, the Application should have a feature which can enable the deletion of the user’s account information. In order to allow your users to delete their account data, please follow the mentioned steps:
Add a delete User Account option in your platform.
When the user selects the delete user account option, display a message to contact your customer support for the deletion of user data. The sample message can be as follows
“We have received your request for account deletion. The deletion process can take upto 2 business days. You will receive a confirmation email at <user’s email> once the request has been processed.”
Once a delete user account request is received, the client shall delete the complete account record and any associated personal data from its database. Please note that deactivating or disabling accounts will not fulfill this requirement.
A user who had previously requested for deletion of their account may try creating a new account. In such cases, the user shall follow the stand sign-up process as it would for new users. You may also choose to prevent a user with a deleted account from signing up again. The recommended message to be displayed in such a scenario is:
"Unable to create an account. Please contact customer support.”
Last updated