7 posts / 0 new
Last post
muneebbaig5979
AVS verification when using REST api with token payments

Hi,

I want to use token based payments. Is there any way to send billing address information and get back AVS codes? I see that in the documentation for credit card payments, but is there any way I can do that for token based payments as well?

If not, then what workarounds do you have? One option I thought of was using the using the Credit Card Payment method to authorize a 0 dollar charge on a card to generate the token and send the billing address at the same time. Does that sound like a correct way of doing this?


rohitrajagopal3538
Re: AVS verification when using REST api with token payments

Muneeb,

Yes, you can include the billing address in the payload to get the AVS. Here is a sample payload -

{
  "merchant_ref": "Astonishing-Sale",
  "transaction_type": "authorize",
  "method": "token",
  "amount": "200",
  "currency_code": "USD",
  "token": {
    "token_type": "FDToken",
    "token_data": {
      "type": "visa",
      "value": "2537446225198291",
      "cardholder_name": "JohnSmith",
      "exp_date": "1030",
      "cvv":"123"
    }
  },
  "billing_address": {
    "street": "123 Woods Street",
    "city": "San Jose",
    "state_province": "CA",
    "country": "US",
    "zip_postal_code": "95133",
    "email": "abc@abc.com",
    "phone": {
      "type": "H",
      "number": "123-123-1234"
    }
  }
}

Here are the field descriptions.

billing_address.street 
(optional)

string

Street address.

billing_address.city 
(optional)

string

City.

billing_address.state_province 
(optional)

string

2-letter state code.

billing_address.country 
(optional)

string

2-letter country code.

billing_address.zip_postal_code
(optional)

string

Zip code.

billing_address.email 
(optional)

string

Email address.

billing_address.phone.type 
(optional)

string

H-Home, W-Work, D-Day, N-Night.

billing_address.phone.number 
(optional)

string

Phone number.


ironplanetengin...
Re: AVS verification when using REST api with token payments

Can you please tell us the way for us to receive AVS code in response to the payeezy.js post to /v1/securitytokens for token based payments, for all card types?

When we implemented AVS verification with token based payments last summer, we did have rejections with most of customer Amex cards. There was an "auth" parameter to be sent to payeezy.js post to /v1/securitytokens which we had set to "true". We had to conditionally set it to "false" to get Amex cards through. Amex cards, I noticed do not bring AVS response after hitting securitytokens url.

I am curious that when I tried some posts on sandbox yesterday, there no longer exists "auth" parameter. Why is that so?

What should I send in the payeezy.js post to /v1/securitytokens url to receive AVS response code for all card types, including Amex cards ?


christopherlord730
Re: AVS verification when using REST api with token payments

The AVS response is no longer supported through Payeezy.JS - You would have to submit a $0 authorization via Direct API to get an AVS and CVV response. Additionally, in the production environment American Express only returns the CVV response if the amount submitted is at least a penny.


ironplanetengin...
Re: AVS verification when using REST api with token payments

We do receive AVS code in the response that returns back the token, for Visa and Mastercards ...

status = 201, response = Object {correlation_id: "124.9521664862229", status: "success", type: "FDToken", avs: "5", token: Object}

Do you mean there is a more recent version of Payeezy.js that does not return this code?


christopherlord730
Re: AVS verification when using REST api with token payments

The AVS verification is not returned all of the time when setting auth=true, especially in production. To ensure you receive a valid response you'll need to submit a $0 authorization via Direct API.


christinespeedy16716
Re: AVS verification when using REST api with token payments

To clarify, yes, the correct way is to perform a 0 dollar auth on a card to generate the token and verify cardholder (CVV, billing address and or 3-D Secure). Once verified, it does not need to be verified again in subsequent token transactions.