Cybersource Developer Community Cybersource Developer Community

vincet · 06-08-2015

The transactions and posting back to our server has been working.We disabled TLS 1.0 on the server and only allow TLS 1.1 or TLS 1.2 This broke the post back and get the following"An error occurred while trying to report this transaction to the merch...

vincet · 01-22-2014

Is this possible? The website/web server collects CC payment and authorize only using DPM. A separate application/server will use CIM to capture the transactions. Do you need customer profiles using CIM to capture transactions?DPM does not create any...

vincet · 08-12-2015

No we have not. We decided to pursue a different payment solution outside of Authorize.net.

vincet · 06-30-2015

@LilithSent the ciphers to Richard at developer@authorize.net.

vincet · 06-26-2015

Hi @Lilith Here are what's enabled and disabled. Note that the only setting that changes is for TLS v1.0 Enabled:TLS 1.1, 1.2 Disabled:TLS 1.0SSL 2.0, SSL 3.0

vincet · 06-26-2015

Hi @RichardH, We just tested it today 6/26/2015 11:45 am cst. The issue still remains.To confirm, we enabled TLS 1.0 and it works.Then we disabled TLS 1.0 and it stops working. -Vince

vincet · 06-24-2015

Hi @RichardH, Any updates on this? Our client's current validation status with American Express DSOP will expire on7/1 and we are hoping to close this issue by then. Thank you.

Cybersource Developer Community Cybersource Developer Community

Your latest statistics

User Activity

DPM fails to post back to x_relay_url after TLS v 1.0 is disabled

Authorize only transaction using DPM Then capture transaction with CIM

Re: DPM fails to post back to x_relay_url after TLS v 1.0 is disabled

Re: DPM fails to post back to x_relay_url after TLS v 1.0 is disabled

Re: DPM fails to post back to x_relay_url after TLS v 1.0 is disabled

Re: DPM fails to post back to x_relay_url after TLS v 1.0 is disabled

Re: DPM fails to post back to x_relay_url after TLS v 1.0 is disabled