Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

Zipmark for ACH? #3491

Closed
chadwhitacre opened this issue May 28, 2015 · 41 comments
Closed

Zipmark for ACH? #3491

chadwhitacre opened this issue May 28, 2015 · 41 comments

Comments

@chadwhitacre
Copy link
Contributor

We're pretty far along with Citizens (#3366), but it's always good to have options on the table. I learned about https://zipmark.com/deposit last night from Andrew Somerville.

@chadwhitacre
Copy link
Contributor Author

Called and left a message for the salesperson that Andrew gave me contact info for.

@chadwhitacre
Copy link
Contributor Author

I filled out the contact form on their website.

@chadwhitacre
Copy link
Contributor Author

Had a phone call. Follow-up scheduled for next Monday. Asked to have someone there that can talk to us about underwriting.

@chadwhitacre
Copy link
Contributor Author

They collect name, SSN, mailing address, email address. Sounds like an iframe flow.

@chadwhitacre
Copy link
Contributor Author

Called back to fast-track, because Balanced deletes information a week from tomorrow. Call set for 2:15 (~45 minutes), to include their founder (@jakehow) as well as their bizdev person.

@chadwhitacre
Copy link
Contributor Author

From a slide deck:

Transparent, Tiered Pricing

volume $/ea
0-500 0.50
501-2,500 0.35
2,500+ 0.25

The monthly minimum of $250 is applied to the first 500 transactions of the month, and
transactions 501+ are billed at the rates noted above.

screen shot 2015-06-04 at 1 37 29 pm

@chadwhitacre
Copy link
Contributor Author

Just got off the horn. Sounds like this might actually work. !m @catskul

@chadwhitacre
Copy link
Contributor Author

Honestly, though, it's a little unsettling that they have no underwriting process whatsoever. After dealing with Citizens (#3366), this feels like a pendulum swing too far in the other direction. :-(

@jakehow
Copy link

jakehow commented Jun 4, 2015

Hey guys. Let me know if you have any questions.

Re: underwriting

I assume gratipay.com is the merchant of record for this app. If you guys go to production you will go through our underwriting process.

Our transactions are eventually routed to our partner banks so we abide by the same restrictions you might see if you go direct we are just much better at helping you through the process and automating the parts that can be.

@chadwhitacre
Copy link
Contributor Author

Thanks @jakehow. We just got rejected trying to go direct (#3366), so it looks like you're our best bet. :)

I've got docs in email from your team, will be following up shortly ...

@jakehow
Copy link

jakehow commented Jun 4, 2015

@whit537 sounds good feel free to send us your emails to developers@zipmark.com for invites to our team slack if you need help.

@jakehow
Copy link

jakehow commented Jun 4, 2015

@whit537 also, make sure you are using the newest docs... http://docs.zipmark.com

If you don't have the login ping us on the same email.

@chadwhitacre
Copy link
Contributor Author

Cool, just emailed re: @rohitpaulk and myself.

@chadwhitacre
Copy link
Contributor Author

@jakehow Yeah, I have the login. I'll share it with @rohitpaulk. When will that be out of beta?

@chadwhitacre
Copy link
Contributor Author

@jakehow
Copy link

jakehow commented Jun 4, 2015

@whit537 its in production we just have not finalized docs yet.

@chadwhitacre
Copy link
Contributor Author

Okay, cool.

@chadwhitacre
Copy link
Contributor Author

@jakehow Looks like webhooks aren't deployed yet? How are failures currently handled?

@chadwhitacre
Copy link
Contributor Author

Note for Gratipay team: Zipmark has a $250/minimum, which at 50¢ per transaction is 500 transactions. We're not going to meet that for a while, which means this is going to be really expensive for us until we do. We were almost up to that level before the Gratipocalypse, and now we're back down to about 25 per month.

@jakehow Any chance you can cut us a break on the minimum for 3 months while we rebuild our userbase? See Gratipocalypse and Gratipay 2.0 for backstory. I'm happy to explain more if need be ...

@chadwhitacre
Copy link
Contributor Author

Re: Webhooks ...

I think that warning may be a little overzealous just because we may adjust the attributes still
I’m looking into how webhooks currently operate as compared to the docs, I’ll let you know when I’m done.

@chadwhitacre
Copy link
Contributor Author

Docs sent to Zipmark.

@chadwhitacre
Copy link
Contributor Author

The webhooks endpoint will work per the docs. The issue is that none of the available resources on the docs are currently enabled to send notifications. For example, you can POST to the webhooks endpoint to create a webhook that will receive notifications, but no events - like say creating a deposit - will not send a notification to the URL of that webhook. We will be working on that and will let you know when we are finished. This is the last piece to get turned on in production and we will keep you posted on its status. Are there any specific needs, concerns, or requirements you have for your webhooks that you want us to know about?

Me:

Thanks, []. The one webhook we're currently using at Balanced is ACH credit failures. How are those currently handled in the absence of webhooks?

@chadwhitacre
Copy link
Contributor Author

Docs sent to Zipmark.

Okay, with that, I'm closing this out! Migration reticketed as #3522, and modifying payday as #3523.

!m *

💃

@chadwhitacre
Copy link
Contributor Author

From: Zipmark

Let's schedule a call tomorrow to go over your business model. We want to make sure that your new model is in compliance with regulations - a measure you seem to have taken. On the call will be Jake, whom you've been communicating with. Does 11am work for you?

Also, we will need an updated bank letter that is addressed to Zipmark.

To: Zipmark

Hah! I knew it. :)

Yes, happy to discuss. I can make 11am tomorrow work, yes. As background for our call, here is Gratipay's risk management program.

I will get you the new bank letter, either tomorrow or Monday.

lol

@chadwhitacre
Copy link
Contributor Author

From: Zipmark

Thanks for being so transparent. Just crossing our Ts and dotting our Is.

Talk to you tomorrow.

@chadwhitacre
Copy link
Contributor Author

To: Zipmark

Thanks for the call. I really appreciate your willingness to help Gratipay clear the bar on BSA/AML compliance. Here is our current review procedure. I'll watch for a list of vendors from you and I'll come back to you with questions as we upgrade our CIP/CDD procedures this next week or so. Our target at this point would be to process on Zipmark on June 18, or June 25 at the latest.

@chadwhitacre chadwhitacre modified the milestones: Balanced shutdown, Pivot Jun 8, 2015
@chadwhitacre
Copy link
Contributor Author

I'll watch for a list of vendors from you and I'll come back to you with questions as we upgrade our CIP/CDD procedures this next week or so.

The list of vendors is included in a sales slide deck I received in private email. I posted a linkified list of the vendors here, but then learned that the list wasn't public, so I've copied to a private repo (https://github.com/gratipay/logs/issues/6) instead.

Please make sure that those are posted privately and not available for public consumption. We're sending you early access information to help get you compliant and we're not ready to notify the world of our third-party integrations.

@chadwhitacre
Copy link
Contributor Author

To: Zipmark

I've moved the list to a private repo, and updated this comment.

Note that we won't ultimately be able to keep the integrations we're using under wraps, for two reasons. First, our code is open source, so whatever third-party vendor(s) we end up using will show up in our public source code repo on GitHub.

Second, and more importantly, I'll need to publicly discuss and decide together with the Gratipay community what vendor(s) we're in fact going to use for AML. Ease of integration with Zipmark would naturally be one of the criteria, but if you're willing to work with whomever we pick, then I guess we can simply pick based on other criteria.

@chadwhitacre
Copy link
Contributor Author

From: Zipmark

Thanks for doing that.

We'll be ready to release that information soon so what you're doing now is fine by privatizing the repo.

@chadwhitacre
Copy link
Contributor Author

From: Zipmark

How is everything coming a long on your end? Do you need anything from me?

I'm out of the office, but I'm available by email and my office line directs to my cell.

Talk to you soon.

To: Zipmark

Thanks for reaching out, []. I was able to connect with [] in Slack the other day, and we have an initial understanding of the work Gratipay needs to do to clear the compliance bar with Zipmark. If you can believe it, we've got a couple even hotter fires to put out this week, after which AML and Zipmark will become our top priorities.

The good news is that we have an extra week with ACH on Balanced (we found out last week). I expect we'll need it in order to achieve our compliance goals before migrating, so our current target is to run ACH on Zipmark on June 25.

Here are the details of our scheduling and prioritization. Let's touch base again early next week.

Thanks! :)

@chadwhitacre
Copy link
Contributor Author

From: Zipmark

Sounds good to me. I'll reach out to you on Monday or Tuesday and we'll work to get you processing [b]y June 25th.

This was referenced Jun 15, 2015
@chadwhitacre
Copy link
Contributor Author

From: Zipmark

Hope you had a great weekend. I briefly skimmed over the links you sent in your previous email. Looks like we need to hammer down an AML solution in order to begin implementation. How have discussions gone on your end? Do we need to schedule another call help facilitate this?

To: Zipmark

Thanks for checking in. I spent the morning reviewing vendors and starting to wrap my head around this project. Comments/questions:

I believe we're primarily looking at four pieces to this puzzle:

  1. individual identity verification
  2. business identity verification
  3. sanction screening
  4. suspicious activity monitoring

Does that match your expectations?

Our ideal at this point will be for Gratipay to implement a program with global reach, even though with Zipmark we'll just be doing ACH for U.S. receivers.

Does Zipmark offer IAT?

What do you understand Gratipay's requirements to be in terms of suspicious activity monitoring and reporting?

Here are the vendors we're currently evaluating for individual IDV and sanction screening:

  1. Trulioo
  2. IDchecker
  3. Veratad IDMatch
  4. Integrity
  5. BlockScore
  6. Jumio
  7. Accuity
  8. IDV Check

Any recommendations or red flags, looking at that list?

Here's where we're looking at business IDV. How does business IDV impact our Zipmark integration?

@chadwhitacre
Copy link
Contributor Author

To: Zipmark

Our best option may be to scrap the Balanced migration data and sign up all users from scratch (we only have 16 users that we've already onboarded on the new Gratipay w/ bank payouts). Can we schedule a call or chat to discuss what that would look like?

How about tomorrow (Thursday) at 11am or 2pm?

h/t @kaguillera @dmk246

@chadwhitacre
Copy link
Contributor Author

Had a call with Zipmark. It turns out that they need to perform identity checks on their side. It's not enough for us to perform the identity checks on our side (#2449, #3557). Any information collection we do on our side would then simply pre-load the workflow in their iframe, and they would hit identity services again. They're going to put together a pricing package for us.

@webmaven
Copy link
Contributor

@whit537:

It turns out that they need to perform identity checks on their side. It's not enough for us to perform the identity checks on our side

Would that mean it would be possible to offload identity checks onto ZipMark entirely?

@chadwhitacre
Copy link
Contributor Author

To: Zipmark

We've decided not to move forward with Zipmark for Gratipay, due to time constraints, the complexity of the task, and the low volumes we're operating at right now. I appreciate your willingness to try to make it happen for us, and especially your feedback on our AML program. Thank you.

You have an export file from Balanced with our users' information. Could you please see to it that that information is securely deleted? Thanks.

@chadwhitacre
Copy link
Contributor Author

Would that mean it would be possible to offload identity checks onto ZipMark entirely?

Not in a simple way, as I understand it.

I've made the call to pull out here.

@chadwhitacre
Copy link
Contributor Author

From: Zipmark

Thank you for the update. I'd like to talk to you about your decision soon so I can get a better understanding of what we can do to help you out. Let's stay in touch because Jake and I both believe that your volume will return to the level that which you had prior to the Balanced shut down.

I'm out of the office today (sick), but I will make sure that the information we received is securely disposed of when I'm back in the office.

@chadwhitacre
Copy link
Contributor Author

chadwhitacre commented Jul 13, 2016

Received in private email:

Subject: Intro: Zipmark and Gratipay

Hi Chad,

I recently came across Gratipay and I wanted to reach out.

At Zipmark, we process payments for a wide range of companies, from on-demand service marketplaces to insurance companies, and to everything in-between. We provide a completely white-labeled solution, which helps our clients replace checks, offers flexible escrow management and enables faster clearing times for ACH transactions.

As a result, we have a lot of experience solving a wide range of payment issues. If your team is experiencing any pain points around its current process, I would be more than happy to set up a call. You can also schedule some time to talk by clicking the "My Calendar" button in my signature line.

Best,

[]


Thanks []. No pain points right now, but I will keep you in mind.

P.S. Here's a record of our history with ZipMark:

#3491

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants