Skip to main content


I was reading the blog of my friend David about Direct Deposit Tithing.  He commented on the prevalence of churches allowing people to auto pay the money to the church (tithe) instead of making them bring a check or cash in an envelope.

Automatic Tithing Machine Before his posts on this I also came across an article about how some churches are installing ATM like machines in the lobby to make giving easier.  That horrified me at first, now I just find it kind of disgusting and annoying.

In any case, at St. Matthew's our contemporary service doesn't take a collection.  Instead we do simply leave an offering plate at the back of the church.  We have also considered a way to directly withdraw from someone's account, though the companies we've seen add on some fees which don't really make much sense.  In many cases people who prefer to pay electronically have their banks automatically send a check.

As a family we still drop a check in the plate after church.  At the same time though, this is the only time during the month that we use cash or checks.  Everything else is directly deposited or checks are sent from the back.  If it were up to me, we'd be tithing to the church in the same way, but for some reason my wife prefers giving this way.  She and I both agree though that giving envelopes are a waste of paper and a horrible treatment of this ecosystem God gave us.

Where I have concerns come partly in the blessing of the money.  I'm not as concerned about that though, since the purpose to which the money is being used is supported by the church and furthers God's mission.  Essentially it's been blessed going out, so it doesn't need to be blessed coming in.  I also sometimes struggle with public blessings of offerings since it could be construed as us focusing on the money instead of the sacrifice.

More than that, I'm concerned that this does offer the opportunity for people to tithe dangerously.  People could begin paying for their tithe using their credit cards so they get more "points" or whatever.  This can easily lead to a credit card not paid off in time or tithing being seen as just another debt to incur.

Overall though, I'm a fan of direct paying.  You know the money is received successfully and no one needs to know if I give weekly, monthly or annually.

As the scripture points out, my tithe is my sacrifice for God.  No one else needs to know about it.



Cindy said…
Wow - ATMs machines? That seems...hmm... that would bother me.

I remember every January, we would pick up our envelope boxes, and you could see who hadn't picked theirs up.

I also thought it was weird, that the church would know who gave and how much they gave. So, if one week you forgot your envelope, but still gave, the church might think you didn't give.

I guess a direct transfer to the church is a good idea - since most banking these days is done that way. but, people might forget about it, or it might be a hassle to change the amount later on. I'm with Erin - I'm a cash person.
ThirstyTech said…
I think having your tithe come out of your account automatically is a perfectly fine option for those that prefer it. I personally lack better organization skills, and having to be at the church early for worship team practice and all the other events I seem to always be rushing around for, there is great comfort in knowing my sacrifice is deducted and submitted despite my flaws and sometimes absentmindedness.

As for the ATM, maybe that's a bit much, but a kiosk? That would be very efficient seeing that there's always some youth retreat or men's or women event to pay fees towards. Plus a kiosk can also provide non monetary transactions such as information, prayer submissions and also leverage whatever features are available on the church website.

Popular posts from this blog

Advantages and Disadvantages of Using Microsoft Access

I've answered this question in some form or another far more times than I care to count.  Most often it's a question of "why do I need a fancy Web application when I can just build this myself in two days in Access.  I mean, the data's already in Excel."  So I figured I'd post out what I threw together, I know I've missed some points. Overview Microsoft Access is an ideal solution for relatively small datasets and a limited number of users. From the Microsoft Web site: “As a desktop database, Access is well suited for small, departmental applications. These applications may start as one user’s project. For example, an employee realizes that productivity can be increased if a paper-based process is automated with an Access application. Other users in the department recognize that they can take advantage of the application if additional features are added. As more features are added, more employees run the application. As time goes by, more and more Access

Beryllium Spheres

I'm sitting here at home watching The Shadow , easily one of the best movies made based on one of the best old time radio shows.  I hadn't picked up on this earlier, but the weapon used to destroy the city is none other than the same power source used to power the NSEA Protector in Galaxy Quest . I never knew Beryllium was so cool.  Now I want a sphere of my own. Anyone know of other places Beryllium Spheres are mentioned? Peace, +Tom

Red-Gate SQL Compare

Every now and then I come across a program that becomes so ingrained in my daily work that I hardly know how I'd get by without it.  I'll probably break down a couple over the next few days, but for database work, I have never found anything as good as Red Gate's SQL Compare and SQL Data Compare .  Essentially these tools let you compare two SQL Server databases (all objects, users, permissions, functions, diagrams, anything) and update changes to whichever database you want.  This is amazingly useful for deploying database changes to a test or production environment (do it to production with ridiculous care, even though it will generate a SQL Script for you and run all updates in one transaction), and making sure everything is synchronized. For releases we can just generate the compare script, confirm that the changes match the updates we want to go out, and store it all in one place with the release details.  This is true for both the structure and the data, to