DPM - Minimum fields required?

[hav]

Looking over the api docs and list of fields, I'm not exactly sure which firelds are required when using DPM - no hosted display at all.

I think I need the following:

x_first_name
x_last_name (which may contain things like "Jr" or "III" etc.)
x_company (possibly blank)

x_address (street)
x_city

x_state

x_zip
x_country
x_phone
x_email

x_method
x_card_num
x_exp_date

x_amount
x_currency_code

x_relay_always
x_relay_url

x_relay_response
x_type

x_fp_hash
x_fp_sequence
x_fp_timestamp
x_invoice_num
x_login
x_method

I do not see a field for the CCV code for the CC?

Are there any other fields I need to include (or consider)?

Are any of the above not really required for DPM? (we DO want AVS)

[RaynorC1emen7]

The min fields required is the same as SIM.

http://developer.authorize.net/api/sim/

There are form settings in the merchant account that you can set for addtional required fields for each transaction.

[hav]

Thanks Raynor - are you referring to pg 25?

I probably asked the question badly.

I see nothing on pg 25 that covers the case where customer name is collected on our side - so I assume in the case of the minimum required fields on pg 25 it is expected that customer name will be collected on an Authnet hosted page or something? yes?

We are collecting all customer info (prior to card num, exp, ccv etc.) so we can better handle the order locally once the transaction is done.  We pass that info on to Authnet in the form which collects card info.

I guess maybe I need to just do some testing to see what happens....

[RaynorC1emen7]

http://developer.authorize.net/guides/SIM/wwhelp/wwhimpl/js/html/wwhelp.htm#href=Appendix%20B.html

All optional are marked optional unless noted.

[hav]

:-) yup - thanks again Raynor - that's where I picked out the ones that seemed to fit. I'll just go start playing in the sandbox a bit and see how those seem to work.  Thanks again!

p.s. - still didn't see anything for the ccv?? did I miss it? I'll go look again.

[RaynorC1emen7]

Look like it missing from the doc, it in the AIM doc, which use the same fields name http://www.authorize.net/support/AIM_guide.pdf

x_card_code

[hav]

Thanks Raynor ... trying to get sandbox going now. When I use my client's credentials I just get

(TESTMODE) This transaction cannot be accepted.

When I test with my sandbox credentials, it stops before the relay (I think) and shows... 

The following errors have occurred.

(13) The merchant login ID or password is invalid or the account is inactive.

Tried posting to https://sandbox.authorize.net/gateway/transact.dll directly but get a bad resource message

so using the https://secure.authorize.net/gateway/transact.dll for testing (my sandbox acct is set to test) ...

Anyway - such is life I guess :-) hanks for the pointer to the AIM list of fields, btw.

[RaynorC1emen7]

For sandbox test account the url is

https://test.authorize.net/gateway/transact.dll

and the test account only work with the test server. Also, turn testmode off on your test account.

[hav · Accepted solution]

Thanks for the tips Raynor.  All seems working now except that an email receipt gets generated from Authnet which we really do not want to happen. Maybe I just need to not send the customer's email addr or maybe it's a setting in the merchant account stuff - but everything else working fine.

Thanks again.

[RaynorC1emen7]

Email receipt is setup at the merchant account. login to the https://sandbox.authorize.net/

Under account settings - email receipt.