10 posts / 0 new
Last post
rickross3779
Not clear on possible values and meanings from several fields (REST/TeleCheck)

I have been making REST calls into the sandbox successfully but have some questions about the fields I am using. I have read the docs for eCheck on the api page but I suspect there is something I am missing. For example :

"check_number": "0101",

I can't fathom why I would need a check number. My clients are online and aren't really using a check.

"check_type": "C",

Are there any other values for this field?

Then, I was quite surprised to find these fields:

"customer_id_type":"1",
"customer_id_number":"7623786df",
"client_email":"username@email.com",

Are those pieces of information about me, the merchant or the person whose checking account will be debited?

Additionally. I don't understand who is in the entire 'Billing Address' section. No ACH transaction I've ever done require email or physical address.

Do please just point me to the right manual if it exists, but I couldn't find this stuff covered anywhere.

Thanks!


rohitrajagopal3402
Re: Not clear on possible values and meanings from several...

Hi Rick,

TeleCheck is slightly different than other forms of direct debit that we see on the web. This is possibly the cause of confusion. Let me explain.

The TeleCheck is one of the payment methods available to customers when they conduct their transaction over a phone call. First, the merchant collects the details of the check over the phone call. After the merchant receives the information from the customer, he/she enters the details of the check along with other customer information. These details are used by the TeleCheck service to conduct a risk assessment and then approve or deny the transaction. This is why we require this information in the payload.

You may read more about TeleCheck here: https://support.payeezy.com/hc/en-us/articles/204059459-What-is-TeleCheck-And-How-It-Is-Used-Within-The-Payeezy-Gateway

Based on the specific business need, merchants may choose to use the TeleCheck service via the TeleCheck REST API or RPM (Real-time payment manager) which is part of the Payeezy solution. The API can be accessed from any of the merchant's applications. 

Regards,

Payeezy Team


rickross3779
Re: Not clear on possible values and meanings from several...

Hi,

Thanks for getting back to me. I think I understood that stuff well enough and would like to do this :

One Time Payment (online)

Hosted Checkout, Payeezy.JS and API use TeleCheck Internet Check Acceptance® (ICA) to process checks in real time. The TeleCheck® ICA service makes it possible to serve customers who prefer to pay for purchases with their checking account online.

If I understand, you are saying that TeleCheck uses the extra fields for risk assessment. Should I conclude then that this is not a 'real' ACH transaction then?

Thanks,

R


rohansureshkumar8148
Re: Not clear on possible values and meanings from several...

Hi

We need to process echeck purchase transactions online, what values should I pass in for the following fields in the request payload JSON:

1. "check_number"
2. "check_type"
3."customer_id_type"
4. "customer_id_number"

We plan to create a form to capture the remaining data from the customer. Additionally, my understanding is that attribute-value pairs inside billing address such as street, city etc. should match the values associated with the bank account. Please let me know if this is correct. Thanks.


rohitrajagopal3538
Re: Not clear on possible values and meanings from several...

Check_Number

The check number being used to complete payment.

Check_Type

Allowed values for this field are "P" (personal check), or "C" (corporate check).

Customer_ID_Type

The type of ID used to validate the identity of the check holder. Allowed values are:

  • Driver's license: 0
  • Social Security Number: 1
  • Tax ID: 2
  • Military ID: 3

Customer_ID_number

Number on the type of identification specified in the previous property.

 

 


rohansureshkumar8148
Re: Not clear on possible values and meanings from several...

Hey Rohit,

1. Since this is online and we don't have a check number or check type. We want to store their information and be able to use it to perform multiple (or even recurring) payments like we do with the payeezy token. In such a case, what should we pass as check_number and check_type?

2. Further, am I right about the billing address details - that they have to match the details on the account as stored by the bank?

3. Finally, with the customer_ID_number, does it have to be formatted in a particular way? For example, should SSN be passed in the format xxx-xx-xxxx or xxxxxxxxx?

Thanks.


manigandansa8714
Re: Not clear on possible values and meanings from several...

Hi Rohit,

My question is same like what Rohan has asked. We have implemented different gateways and we know when it comes to ACH there are 2 ways to do it. One use the Account number , routing code and Check Number , which is fine and which works in Payeezy . But what if the customer has given only the Account number and routing code . they want to charge the one time payment . Then how do we handle this . We seen this functoinality in the different gateways , but can you confirm if payeezy supports this or not. There is already a customer who bought Payeezy as their merchant account and they expecting this to work like that. So I just want to know whether there is a functoinality like this or not. Because whenever we tried without a Check Number , it is always throwing a error saying Check Number is missing .


rohitrajagopal3538
Re: Not clear on possible values and meanings from several...
  1. For recurring payments, the check number is only required by the API call (due to it being required for non-recurring), so you can set this to anything you like, but I recommend using the payment number. Check Type you will need to get from the customer on the first payment and then send that same value on each subsequent payment.
  2. While you may obtain an authorization with incorrect address information, the details provided should match what is on the check.
  3. The customer ID number should only contain alpha-numeric characters. Any punctuation should be removed.

rohansureshkumar8148
Re: Not clear on possible values and meanings from several...

Thanks.

1. What do you mean by payment number? Since we are doing this online, we are not using a physical check even for the first non recurring transaction.

2. Further, do we need to pass the eci_indicator in the payload for recurring check transactions as we do for recurring token transactions?

3. Is a 0$ authorization possible?


rohitrajagopal3538
Re: Not clear on possible values and meanings from several...
  1. By Payment Number I mean the count of the number of times you have charged the customer and submit that as the check number. For example, the first time you charge a customer, you would use “1”; the second, “2”; etc.
  2. Yes, you must pass the eci_indicator field as “2” for recurring check transactions
  3. No, it is not possible to process a $0 Auth for Checks.