Providing an ACH Payments Website Payments Solution can Provide Many Benefits for Various Organizations and Businesses. Here’s how to do it.

Providing ACH website payments solutions for organizations can include a multitude of requirements. Here at ACH Payments, we have a number of tools and integration methods that will likely meet the vast majority of organizations and businesses who have determined that they would benefit from accepting not just ACH payments from their website, but also credit card transactions. Let’s examine some key areas of interest for adding an ACH website payment solution:

Topics:

1. Security and Integration
2. User Experience
3. Subscription Based Payments
4. Pricing
5. Reporting
6. Conclusion

Security and Integration

Yes, we have all heard about the major retailers who have been compromised and credit card sata has been stolen. What we don’t hear about are the small websites that are compromised. Keep in mind that ACH transactions are not subject to the same PCI requirements that credit card transactions are, but nevertheless, both types of transactions contain sensitive data – and yes, bank account data from compromised websites is sold by data thieves and used nefariously by other unsavoury individuals.

In 2016, PC Magazine reported that almost 6,000 online shops had been compromised. While most of these shops that were compromised were using https or third party payment processors, those mitigation methods don’t protect against malicious javascript code injection. Malicious code is injected by security vulnerabilities and captures sensitive data that’s exposed.

Protection of sensitive data should be paramount to an organization who wishes to accept payments via their website. Above and beyond running on https, how the website payment integration communicates, or how the website payment utility being employed works is key to mitigating data theft.

Here at ACH Payments, we have utilities and integrations that can greatly reduce and even eliminate the risk of data theft; for both ACH transactions and credit card transactions. In all methods we have available, tokenization can be used. In some cases sensitive data never touches a using organization’s web server. Instead, sensitive data is posted directly to a PCI level 1 gateway which simultaneously returning a reference token that replaces the need to store the sensitive data. In such a scenario it’s completely impossible for nefarious intrusions to compromise sensitive data from the using organization’s web server.

There can be multiple options for integrating a payment solution for a website or web application. An API integration makes sense in many use cases, while a javascript modal utility can work quite well in a lot of use cases. The javascript modal utility prevents your webserver from ever touching or storing sensitive data, therefore reducing the PCI scope. While integrating with the API solutions does cause your webserver to initially touch sensitive data, that data is quickly replaced (a second or so) with a reference token to be used for subsequent transactions.

User Experience

How a payments page is presented to visitors is of great importance to organizations who want to accept payments via their website. Integration with the using organization’s database can allow for various fields to be populated upon arriving at the the actual payment submission page or modal, saving time from dealing with data errors submitted by visitors. Likewise, pre-populated data, whether visible or hidden, can make reconciliation a much simpler task, e.g., a hidden transaction number or account number.

Moreover, how the payments page appears to a visiting customer has a role in adoption. Redirection to a third party url might be fine for some organizations, but for others it simply doesn’t meet their needs. They know that a visiting customer must stay on their website URL and not be redirected for payment and then redirected back once the payment has been made.

The ability to allow and or control various options for payment acceptance can be beneficial to not only the visiting user, but also the integrated organization. For example, an organization with a recurring billing model might want the ability for the customer to configure their own recurring payments, but with limitations. An example of this might be that the consumer has a total payable amount of $300 that would be set as not editable, but there might be a choice allowed for the consumer to pay the total amount due over 2,3 or 4 months. Or, the total of $300 might be configured to be paid as either a single one-time transaction or split over 3 months – with the choice provided to the consumer. Other things like the start date of the transaction or the frequency can be editable if the integrating organization chooses to do so, e.g., pay monthly, bi-monthly or weekly.

No matter the use case, ACH Payments has you covered with a number of website payment options, from the aforementioned redirect to SOAP and RESTful integrations and javascript modals that transmit directly to the gateway.

Subscription Based Payments

Any organization that has a subscription based product or service that includes recurring payments generally has a need for ACH Payment acceptance. While many subscription based needs are setup manually by the merchant organization, some have the need for their visiting customer to setup the recurring payments themselves. Doing so requires that the integration or website utility used is capable of scheduling and managing recurring payments functionality.

Here at ACH Payments, we have the functionality for an organization to empower their website to accept, schedule and manage subscription, recurring based payments from their user base of customers.

ACH transactions are practically a must form businesses with recurring payments needs. Credit card declines average 15% in the recurring space. These declines come from expired credit cards, compromised or stolen cards and newly issued EMV cards. The amount of work that some organizations have to go through to re-capture new card data is a daunting task. While there are now tools to use like the credit card updater networks, there are transactional costs to those. Even then, the likelihood of all declines being updated is next to zero. Bank accounts don’t have expiration dates, and the percentage of rejected items from closed accounts in the subscription sector is far lower than credit card declines.

While a company must meet the need of their users in so far as what payment options are offered, having multiple payment modals is likely a wise choice – especially for a subscription based model. For example, having both a credit card and a checking account on file for customers can prevent wasted customer service time in chasing down new credit card information. Instead of chasing that credit card information down, the checking account could be debited if both accounts happen to be stored (as tokens).

Pricing

The costs from accepting ACH transactions is far less than accepting a credit card transaction. Given that the subscription sector knows their customers far better than a business’ website that is shaped more towards one-off transactions, ACH payments make a great deal of sense. Subscription based customers generally rely on the product or service being delivered by the business. In some cases it’s a delivery of a recurring item, and in other cases it’s a virtual service – which are easy to terminate access to, eliminating product loss revenues. Consider the cost difference: A subscription based business with 1,000 customers paying $75 per month via credit card amounts to ~$2,200 per month in processing costs. That same customer base using ACH would amount to ~$290 per month in ACH processing costs; an annual savings of ~$23,000.

Many ACH processors charge a percentage of the transaction amount to the ACH processing fee. In most cases, here at ach-payments.com, we charge a flat rate for transactions. This flat rate pricing becomes advantageous with average transactions amounts above $45. Below that amount it’s nearly identical for the bottom-line.

Of course we also offer credit card merchant accounts, and we certainly don’t want to downplay the importance of the credit card rail. It’s the most widely used form of electronic payments for websites. In some cases eCheck transactions simply don’t make sense for a given website. Pricing for credit card merchant accounts can vary slightly depending on the product or service sold and what the average sale ticket is. Pricing can be configured as tiered, interchange plus or as a flat rate.

Reporting

You need to know the status of your ACH transactions. There should be multiple methods for obtaining transaction status for reconciliation. Look for the ability to download multiple data formats in order to reconcile. Notifications are also important. Being able to assign users various permissions that send them email notifications are critical in instances such as NSF returned items. Moreover, notifications to customers can be very important.

How the reporting data gets back to your organization is likely important. In some cases it might be acceptable to download a daily or weekly file. But in some use cases it’s important to be delivered near instant status updates of the transaction cycle. That’s were employing webhooks can be advantageous. Webhooks are postback messages that are delivered to unique url’s that are configured for a given organization’s use case.

One huge advantage is being able to reconcile funding deposits to the transactions that comprised the bank deposit. Read more about Payment reconciliation.

Conclusion

If you are looking for a product or tool for accepting online payments, you have come to the right place. Our Secure Website Payments tools are easy to use, secure and can get you up and running quickly.

Some of the features included are:

• Merchant definable fields.
• Custom branding to match your site (hosted solution).
• REST API integration
• SOAP integration
• Javascript modal website payment utility
• Merchant controlled receipts and email notifications.
• Integrated webhooks for transaction event updates.
• Integrated reporting and reconciliation.
• Can accept both e-checks and credit cards.
• Option for future or recurring payments.

ACH Payments has been assisting businesses and organizations of all sizes with website payment integrations for over 20 years. If you’re looking for a solution for accepting payments on your website, contact us and we’ll guide you through the options and help you decide the best option for you and your company.

What SMS Payments Are and How Can They Benefit an Organization in 2023

This overview is focused on payments being made by a consumer to a company or an organization by way of the company sending an outbound SMS message to their customer, requesting a payment.

Topics:

• What is an SMS Payment Solution?
• How does SMS Payment Processing Work?
• Business Benefits to an SMS Payment Solution
• What to Look for in an SMS Payment Solution
• How to get Started with SMS Payments

What is an SMS or Payment by Text Solution?

Unless you have been asleep for the last ten years you know what an SMS is – commonly referred to as a text message. An SMS Payment solution allows companies to notify customers with payment reminders and accept payments from customers or donors via a cellular connected mobile device.

Chances are that if you have a mobile phone and are not subscribed to a recurring payment plan, you have likely received an SMS message reminding you that your monthly invoice is past due with an option to remit payment.

SMS messaging is limited to 160 characters, but that is generally more than enough needed to send an SMS Payment reminder.

Recent research shows that the majority of financial transactions conducted across the globe are via SMS, and the volume continues to grow at a rate exceeding 25%. While some large organizations have already adopted SMS as a payment solution, smaller organizations are just starting to wake-up to the possibilities of how SMS can reduce their labor costs and increase their on-time receivables.

SMS Payment technology has now become affordable for even the smallest of companies. What normally costs a company to receive a payment through a customer service channel over the phone can exceed $5 in some instances because the cost is tied to an hourly labor rate, plus overhead and employee benefits. An SMS Payment solution can reduce the cost to under $0.50.

From a cost standpoint alone, any company having monthly receivables due should consider SMS Payments, especially a company with a late payment problem that is in need of being reduced. Being able to text message your customer puts a reminder right to the device that most carry with them at all times. If nothing else, companies should start collecting cell numbers of their customers for the day that the need to start implementing an SMS Payment solution.

How Does SMS Payment Processing Work?

As it relates to Payments, SMS can either:

1. Send an outbound message that provide the ability for a company or an organization to collect funds owed by customers via their cellular device by replying “Call,” which triggers an outbound IVR call to the customer and allow the customer to remit a payment via the IVR Payment system.
2. Provide a link in the SMS message that sends the customer to a payments page that renders on their mobile device’s browser. The URL displayed can be external or a subdomain of the SMS sender. The payments page provides the ability for the customer information and amount owed to be pre-populated and provides and number of security options such as account number entry for customer verification purposes.

In most cases an SMS payment solution that is implemented requires that the customer agree to terms that allow the company to begin sending them text messages for receivables that are due. Once implemented, an SMS payment solution to receive messages that contain information such as amount due, past due date and balance information. Your customers will also appreciate the notifications and the convenience of either paying through their mobile device’s browser or by opting for an IVR system to initiate an outbound call to them.

Having the two options provides some security comfort for differing mindsets of the customer base. Some don’t trust remitting funds on a mobile device’s browser, but might feel more comfortable with an IVR call. The API integration capabilities of being able to present things like a customer account number, a rate plan, start date or simply the amount due adds to consumer confidence with either choice.

What are the Business Benefits of an SMS Payment Solution?

• Reduced labor. In a recent discussion with a current client who is now implementing an SMS solution (and an IVR Payment solution), it was learned that the volume of their current phone calls into the company, that 40 percent of the calls are from customers calling in to remit a payment and the number of payment made over the phone average 1,800 per month. While we’re not yet sure what the savings will be by implementing SMS and IVR for payments, it’s undeniable that the dollar amount put back to their bottom-line will be significant.
• Customer satisfaction. An SMS payment solution can remember a user who has previously made a payment using the system. This is done securely using a stored payment token that has replaced the sensitive credit card or bank account data. This improves the time required by the customer to complete the transaction. Instead of having to find their wallet or purse and get their physical credit card, the SMS payment system can pre-populate the card number field with the last four digits of their previously used card and ask them if they wish to use the same payment method. Electronic, PCI compliant methods of payment acceptance are more secure than a customer service representative talking a credit card payment over the phone, and most all customer know that and appreciate those additional channels for remitting payments.
• Increased rate of on-time payments. Most consumers don’t want their payables to be late, but some times they simply forget. No matter the case, an SMS solution for presenting a reminder to pay to a customers’ mobile device, even if they don’t use one of the SMS payment options will remind your customers that they have an invoice to pay.
• Reduction in paper. With all the available electronic notification and payment methods available today, there’s little reason to keep mailing invoices for many companies. An SMS solution adds another tool in the payments options box to further reducing the amount of paper invoices produced and mailed.

And there’s also benefits to the customer!

• Ease of use is huge. As mentioned above, not having to go find a credit card – assuming a prior system payment has been made. Even if not having made a prior payment, the system is easy to use and provides a very convenient way for a consumer to remit a payment.
• The customers don’t have to file and remember a paper invoice. Notifications can be automatic and sent according to your scheduling.
• It’s a secure transaction processing environment. Protecting sensitive data is one thing, but never knowing it is even better. An SMS payment solution using Zero Knowledge architecture only touches sensitive data for a brief instance, and the manor in which it is briefly stored is via volatile RAM, not accessible to any potential theft of data. Moreover, the system is completely PCI compliant. Only the payment gateway stores the data, and that’s PCI Level One compliant.

What to Look for in an SMS Payment Solution

• Data population options. Technically savvy companies will likely want to populate the SMS payment system via an API integration to their existing ERP or CRM solution. API integration capability provides the most options for how and what information is utilized with the SMS solution. There should be the ability to self-integrate and also the option for the SMS solution to integrate to your organizations’ API. For smaller and less technically savvy companies, the ability to populate the SMS solution via a csv file upload should be available. While this doesn’t provide the automation that an API integration does, the amount of work involved is minimal. It can be as simple as exporting relevant data from an ERP or CRM system and importing it to a secure hosting environment that the SMS solution can call for data population.
• Powerful User Interface. An SMS payment system should provide the using organization with tools to make changes as they deem necessary, without the involvement of the SMS solution provider. For example, if the organization wants to make a change in a message script, they should be able to login to the SMS user interface and easily perform the task themselves. Some SMS/IVR solution providers charge large fees to make these changes.
• PCI Compliance. As mentioned earlier, the SMS solution should be PCI compliant. Even better would be the fact that it uses Zero Knowledge architecture.
• Telco infrastructure and quality. The SMS provider should have the ability to mass send SMS messages with no throttle limitations. Numbers should be available for your countries of choice, toll free numbers and the ability to port a number of your choice.
• Workflow environment and configuration. The SMS provider should be able to configure complex workflows for the triggered outbound IVR calls and the flow should be visible in a user interface that is understandable. The ability to branch a flow in order to A/B test the effectiveness of those branched flows should be available.
• Reporting. The using organization should be able to see and know the SMS messages that were delivered, undeliverable and the transactions that were completed. Insist on a Transaction Funding Report; a report that easily reconciles each and every transaction that is associated with a funding deposit to your bank account.

How to Get Started

Easy! Contact us and let’s discuss your current receivable environment, your goals and how you might be able to start implementing  an SMS payment solution.

How  SaaS platforms can leverage an ACH Payment Gateway to grow revenues and create better customer solutions

Content:

1. Security and the prevention of sensitive data theft
2. Transaction automation
3. Notification
4. Authentication and verification tools
5. Merchant on-boarding experience
6. Multiple payment modals
7. Integration
8. White label gateway and processing

First and foremost, integration of a software application for enabling it to originate and report back on the ACH transactions stands to benefit greatly. This is accomplished by integrating to the ACH Payment Gateway API. But exactly what advantages or functionality does this provide over batch transmission? Let’s review some of the advantages:

Security; Prevention of Sensitive Data Theft

Batch transmission transmits the complete bank routing number, bank account number and the name of the account holder. While sFTP is a secure method of transmitting files, the fact remains that the sensitive data is stored somewhere within your organization’s IT infrastructure, thus potentially exposed to being compromised by outside operators. Moreover, employees come and go, and who’s to say that one single disgruntled employee might walk away with that data. An ACH payment gateway can eliminate these risks.

The ACH payment gateway receives an initial customer record that includes the bank account data and then posts back a reference token to be stored by the software application, removing the sensitive data. Therefore, no sensitive data need ever be stored on the organization’s IT infrastructure. Subsequent ACH transactions are posted using the stored reference token instead of the sensitive data. The sensitive data is stored in a PCI level one compliant system.

Currently there is no requirement for ACH transactions to be subject to PCI requirements like there is for credit card transactions, but there should be. ACH and credit card data both amount to financial loss if sensitive data is compromised. Why there isn’t such a requirement is most likely because mandating such a requirement would mean a lot of work for tier two and tier three financial institutions that don’t have the IT capabilities of the tier one financial institutions like Bank of America, Chase, Wells Fargo, etc.

Transaction Automation

API integration with the ACH payment gateway can automate a number of transactional tasks. Applications having a subscription component, or recurring transactions, are common users of ACH processing for a variety of reasons. The ACH gateway API can automate the origination of these recurring transactions for a set it and forget it scenario. Doing so greatly reduces manual time involved in creating a file such as in a batch submission scenario. This automation can be left to be managed by the ACH gateway API, as it has objects for schedules and schedule_items. Using those objects pushes the recurring transaction tasks off to the ACH gateway to manage, yet the ability to change a schedule or modify amounts, including for single transactions remains.

While some development teams do rely on the ACH gateway’s schedule objects to manage their recurring transactions, some opt to programmatically manage that functionality within their application itself. This, too, can be accomplished via the gateway API. Use cases generally point to one direction or the other.

Unique ACH Reconciliation capabilities allow the SaaS platform to reconcile bank deposits to client reporting

Notifications

A number of notifications can be triggered via the ACH payment gateway integration, including internal notifications, organization notifications and settlement notifications. For example, an origination notification might instantly return back an invalid TRN notification letting an application user know that the TRN is invalid. A settlement notification can be returned letting accounting know that a transaction has been considered settled, thus posted to their account. Another use for settlement notifications would be to let internal personnel know it’s okay to ship goods. Likewise, late returns and chargebacks can be configured for notifications and allow for internal personnel to track transactions that consumers dispute.

Near real-time notifications can be integrated via the integration API webhooks functionality. Webhooks are post-back messages that can be configured to send these messages to server-side URL endpoints. Implementing webhooks can provide automated updates to occur within your integrated application for such things as transaction events, e.g., updating the status of an ACH transaction to settled or returned for NSF reasons.

Authentication and Verification tools

Verification services can be called to assist a merchant with risk mitigation on ACH transactions. Options range from simple TRN validation and negative database checks to real-time inquiries into account status that allows the merchant user to know if an account is open or closed and has a positive or negative balance. Some applications require additional verification information like account balance. Account balance is possible, but currently it requires a consumer provide account login credentials to the financial institution’s online system.

Authentication of bank accounts is also possible and provides merchants with the ability to know that the person presenting bank account credentials actually owns that account, matching name or business name with the bank account credentials.

Merchant On-boarding Experience

Many SaaS applications are built to serve multiple businesses, and they want as few choke points as possible for user adoption. The ACH Payments Gateway API can provide a white label experience to the merchant users when applying for ACH processing services. The API allows the SaaS application to embed the application process within their website or mobile app, transmitting the application data to our underwriting team for approval.

Many applications leave it to their user base to create API keys from our web portal and enter the keys themselves for activation. However, using the merchant application API this process can enable functionality for the enrollment team and its process to automate a credential push to the SaaS team for entering API keys on their end. Generally, the use case determines the proper method for the organization and its users.

The application and boarding process can be presented on the integrated partners’ website or application. The same API that provides the ACH payments origination and reporting functionality also contains parameters for on-boarding customers that serve a vertical client base. Underwriting details like Business name, DBA, officers are completed and supporting documents are facilitated using a documents object. Once the new client has been on-boarded, the integrated application can then call the necessary API keys and activate their new client for ACH processing within their application.

Multiple Payment Modals

While there are some applications that solely use ACH transactions as their method for payment acceptance, credit cards aren’t going away anytime soon. Credit cards are still the most widely used payment modal for remote transactions, and to dismiss the need for them would seem silly. It would also be silly to have to integrate to multiple gateway API’s to facilitate both payment modals, assuming a single gateway can facilitate both. For that we have the answer. While we started out some 19 years ago in the ACH space, we quickly enhanced our offerings to include credit card processing. We can provide you a single gateway integration that covers both the ACH and credit card payment modals.

ACH Payments has been providing ACH gateway integrations to organizations of all sizes for 19 years. Contact us to discuss your integration needs and let us help you find the right mix of tools and services to meet your needs.

Integration

Integration of an ACH payment gateway provides the ability for a software platform to embed payments functionality into their platform. The ACH payment rail is especially ideal for applications having a recurring payments component, but not necessarily limited to recurring. The ACH rail can also be extremely beneficial for disbursements to partners, vendors – or even for internal use, e.g., payroll.

Integration can be accomplished by way of a number methods. REST API, XML API Guide or language specific SDK’s. Depending on the integrating organization’s needs, more simple methods of integration are also available such as website payment utilities, either hosted and branded, or javascript payment modals that reduce the PCI scope of the software being integrated.

Integration by a software platform also can provide an additional revenue stream to the integrating organization, and while still providing as good or better than current market rates.

One of the major benefits of ACH gateway integration is the reduced costs associated with the ACH payment rail. Unlike credit card transactions, we charge no discount fee for transactions originated by credit-worthy organizations. If your application serves a vertical base of low risk clients, providing an ACH payment gateway integration will provide your client base with a value add service that can save them up to 90% in processing costs.

White Label Gateway and Processing

The ACH Payment Gateway has the ability to be utilized by other third party processors or financial institutions. Capabilities can include risk mitigation tools like transaction limits and velocity settings, both with notification functionality as well as dashboard views. Merchants can be boarded via API. Merchant processing origination capabilities include the same as we provide, but in a white label environment. Typically an minimum number of monthly transactions are required. However, for newer organizations a setup fee can offset minimums. Multiple configurations are possible for third-party use. Banks and credit unions are encouraged to check with us for potential solutions that might benefit their organization or their business customer base. It’s mandatory to have an initial requirements discussion to go over your organization’s needs in order to arrive at costs. Please contact us.

Get Connected!

An ACH Payment Gateway integration provides the ability to better serve your client base and securely connects your platform for ACH processing. For any platform that serves it’s client base with a recurring payments component, an ACH integration is a must. If your subscription based application isn’t integrated for ACH processing, you’re not providing a component that is likely needed by your users. Now is the time to get your application connected with an ACH Payment Gateway integration. Here at ACH Payments, we have been meeting the ACH integration needs for businesses of all sizes for 20 years. Contact us and let us assist you with the right ACH gateway integration needs for your user base.

test

Terms of Service for ach-payments.com

Introduction

Welcome to ach-payments.com. This website is owned and operated by ach-payments.com. By visiting our website and accessing the information, resources, services, products, and tools we provide, you understand and agree to accept and adhere to the following terms and conditions as stated in this policy (hereafter referred to as ‘User Agreement’), along with the terms and conditions as stated in our Privacy Policy (please refer to the Privacy Policy section below for more information).

This agreement is in effect as of Jan 21, 2019.

We reserve the right to change this User Agreement from time to time without notice. You acknowledge and agree that it is your responsibility to review this User Agreement periodically to familiarize yourself with any modifications. Your continued use of this site after such modifications will constitute acknowledgment and agreement of the modified terms and conditions.

Responsible Use and Conduct

By visiting our website and accessing the information, resources, services, products, and tools we provide for you, either directly or indirectly (hereafter referred to as ‘Resources’), you agree to use these Resources only for the purposes intended as permitted by (a) the terms of this User Agreement, and (b) applicable laws, regulations and generally accepted online practices or guidelines.

Wherein, you understand that:

a. In order to access our Resources, you may be required to provide certain information about yourself (such as identification, contact details, etc.) as part of the registration process, or as part of your ability to use the Resources. You agree that any information you provide will always be accurate, correct, and up to date.

b. You are responsible for maintaining the confidentiality of any login information associated with any account you use to access our Resources. Accordingly, you are responsible for all activities that occur under your account/s.

c. Accessing (or attempting to access) any of our Resources by any means other than through the means we provide, is strictly prohibited. You specifically agree not to access (or attempt to access) any of our Resources through any automated, unethical or unconventional means.

d. Engaging in any activity that disrupts or interferes with our Resources, including the servers and/or networks to which our Resources are located or connected, is strictly prohibited.

e. Attempting to copy, duplicate, reproduce, sell, trade, or resell our Resources is strictly prohibited.

f. You are solely responsible any consequences, losses, or damages that we may directly or indirectly incur or suffer due to any unauthorized activities conducted by you, as explained above, and may incur criminal or civil liability.

g. We may provide various open communication tools on our website, such as blog comments, blog posts, public chat, forums, message boards, newsgroups, product ratings and reviews, various social media services, etc. You understand that generally we do not pre-screen or monitor the content posted by users of these various communication tools, which means that if you choose to use these tools to submit any type of content to our website, then it is your personal responsibility to use these tools in a responsible and ethical manner. By posting information or otherwise using any open communication tools as mentioned, you agree that you will not upload, post, share, or otherwise distribute any content that:

i. Is illegal, threatening, defamatory, abusive, harassing, degrading, intimidating, fraudulent, deceptive, invasive, racist, or contains any type of suggestive, inappropriate, or explicit language;
ii. Infringes on any trademark, patent, trade secret, copyright, or other proprietary right of any party;
Iii. Contains any type of unauthorized or unsolicited advertising;
Iiii. Impersonates any person or entity, including any ach-payments.com employees or representatives.

We have the right at our sole discretion to remove any content that, we feel in our judgment does not comply with this User Agreement, along with any content that we feel is otherwise offensive, harmful, objectionable, inaccurate, or violates any 3rd party copyrights or trademarks. We are not responsible for any delay or failure in removing such content. If you post content that we choose to remove, you hereby consent to such removal, and consent to waive any claim against us.

h. We do not assume any liability for any content posted by you or any other 3rd party users of our website. However, any content posted by you using any open communication tools on our website, provided that it doesn’t violate or infringe on any 3rd party copyrights or trademarks, becomes the property of ach-payments.com, and as such, gives us a perpetual, irrevocable, worldwide, royalty-free, exclusive license to reproduce, modify, adapt, translate, publish, publicly display and/or distribute as we see fit. This only refers and applies to content posted via open communication tools as described, and does not refer to information that is provided as part of the registration process, necessary in order to use our Resources. All information provided as part of our registration process is covered by our privacy policy.

i. You agree to indemnify and hold harmless ach-payments.com and its parent company and affiliates, and their directors, officers, managers, employees, donors, agents, and licensors, from and against all losses, expenses, damages and costs, including reasonable attorneys’ fees, resulting from any violation of this User Agreement or the failure to fulfill any obligations relating to your account incurred by you or any other person using your account. We reserve the right to take over the exclusive defense of any claim for which we are entitled to indemnification under this User Agreement. In such event, you shall provide us with such cooperation as is reasonably requested by us.

Privacy

Your privacy is very important to us, which is why we’ve created a separate Privacy Policy in order to explain in detail how we collect, manage, process, secure, and store your private information. Our privacy policy is included under the scope of this User Agreement. To read our privacy policy in its entirety, click here.

Limitation of Warranties

By using our website, you understand and agree that all Resources we provide are “as is” and “as available”. This means that we do not represent or warrant to you that:
i) the use of our Resources will meet your needs or requirements.
ii) the use of our Resources will be uninterrupted, timely, secure or free from errors.
iii) the information obtained by using our Resources will be accurate or reliable, and
iv) any defects in the operation or functionality of any Resources we provide will be repaired or corrected.

Furthermore, you understand and agree that:

v) any content downloaded or otherwise obtained through the use of our Resources is done at your own discretion and risk, and that you are solely responsible for any damage to your computer or other devices for any loss of data that may result from the download of such content.
vi) no information or advice, whether expressed, implied, oral or written, obtained by you from ach-payments.com or through any Resources we provide shall create any warranty, guarantee, or conditions of any kind, except for those expressly outlined in this User Agreement.

Limitation of Liability

In conjunction with the Limitation of Warranties as explained above, you expressly understand and agree that any claim against us shall be limited to the amount you paid, if any, for use of products and/or services. ach-payments.com will not be liable for any direct, indirect, incidental, consequential or exemplary loss or damages which may be incurred by you as a result of using our Resources, or as a result of any changes, data loss or corruption, cancellation, loss of access, or downtime to the full extent that applicable limitation of liability laws apply.

Copyrights/Trademarks

All content and materials available on ach-payments.com, including but not limited to text, graphics, website name, code, images and logos are the intellectual property of ach-payments.com, and are protected by applicable copyright and trademark law. Any inappropriate use, including but not limited to the reproduction, distribution, display or transmission of any content on this site is strictly prohibited, unless specifically authorized by ach-payments.com.

Termination of Use

You agree that we may, at our sole discretion, suspend or terminate your access to all or part of our website and Resources with or without notice and for any reason, including, without limitation, breach of this User Agreement. Any suspected illegal, fraudulent or abusive activity may be grounds for terminating your relationship and may be referred to appropriate law enforcement authorities. Upon suspension or termination, your right to use the Resources we provide will immediately cease, and we reserve the right to remove or delete any information that you may have on file with us, including any account or login information.

Governing Law

This website is controlled by ach-payments.com from our offices located in the state of NY, United States. It can be accessed by most countries around the world. As each country has laws that may differ from those of NY, by accessing our website, you agree that the statutes and laws of NY, without regard to the conflict of laws and the United Nations Convention on the International Sales of Goods, will apply to all matters relating to the use of this website and the purchase of any products or services through this site.

Furthermore, any action to enforce this User Agreement shall be brought in the federal or state courts located in United States, NY You hereby agree to personal jurisdiction by such courts, and waive any jurisdictional, venue, or inconvenient forum objections to such courts.

Guarantee

UNLESS OTHERWISE EXPRESSED, ach-payments.com EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

Contact Information

If you have any questions or comments about these our Terms of Service as outlined above, you can contact us at:

ach-payments.com
15 Ingersoll Rd.
Saratoga Springs, NY 12866
United States