Exactly how does DPM work?

[jaredsmark1]

I've searched but couldn't find exactly what I was looking for. I understand that somehow the CC info that's entered on your site is 'POSTed'  (not sure what that means) to the authorize gateway directly, bypassing your server, but is that because the CC fields are actually generated by authorize and they're inserted into your pages, or does it work some other way?

I did see some random video where it appeared that CC info was entered on the person's site, then there was a quick redirect to the authorize gateway (blank page) and back to the person's site again.

I've looked for an online demo of the DPM method but couldn't find one. I'm curious if the receipt page is generated by authorize or you can make your own as well.

[RaynorC1emen7]

http://developer.authorize.net/api/howitworks/dpm/

Your site generate the CC form, and send it to your customer browser. When they hit submit, the CC form info is post to authorize.net and not to your website.

you can either use the receipt page from authorize.net or create your own and set it in the relay response url

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

[jaredsmark1]

So there IS a redirect to the Authorize site, and then another back to your site (if you choose to use your own receipt page) right? I saw a video demo that showed a blank white page with the authorize link in the browser, but the link to the manual you posted says otherwise.

By the way, is POST an acronym for something?

[RaynorC1emen7]

If you are using relay response. after the customer hit the submit to post CC info to authorize.net. authorize.net send it to process and get response. then they relay the response to your relay response url. the relay will be on their site(the url stay at https://secure.authorize.net/... , so if you want to get it back to your site for the receipt, do a javascript redirect on that.

Relay Response Basics and Troubleshooting

By the way, is POST an acronym for something?

<FORM action="http://somesite.com/something" method="post">

[jaredsmark1]

Still a little confused. By your post it seems that the flow is like so:

Customer clicks place order

card info is sent to Authorize

user's browser goes to authorize (briefly) as processing takes place

authorize sends transaction results to relay url and sends user's browser to relay url as well

the relay url contains code that redirects the user's browser to wherever you want.

Correct?

[RaynorC1emen7]

Sound about right.