authorize.net

问题 I'm hoping discuss how to use Magento 2 and Authorize.net in a way that removes most the PCI compliance risk. The Magento 2 Direct Post Method (DPM) appears to still contain a high level of risk and requirements. Our setup: Authorize.net was setup by our bank and had us use TrustWave to validate our PCI risk/compliance. We are currently using Authorize.net as the payment gateway and using the Out-Of-The-Box Authorize.net DPM module. One of the questions in the TrustWave questionnaire asks: Do

问题 I am using Authorize.net as a Payment vendor in my application. After getting form token from Mobile SDK, I am using their Java SDK in Backend to initiate Payment. But I am getting the following issue while using CreateAnAcceptPaymentTransaction class from Authorize.net Java SDK(v2.0.1). Environment not set. Set environment using setter or use overloaded method to pass appropriate environment The controller object in the below line has the error. CreateTransactionController controller = new

问题 Authorize.Net Direct Post for Magento Getting below error. An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card. This transaction has been approved. It is advisable for you to contact the merchant to verify that you will receive the product or service. 回答1: This means the relay response URL used by Magento/your website is not

问题 I ran into the recent Authorize.net SSL certificate invalidation debacle last week. I've been able to get curl to accept their certificate finally: $ curl -Iv https://secure.authorize.net ... * SSL certificate verify ok. ... but python is still rejecting it with requests: >>> requests.get('https://secure.authorize.net', verify=True) ... InsecurePlatformWarning and in my code: File "/usr/lib/python2.7/ssl.py", line 405, in do_handshake self._sslobj.do_handshake() SSLError: [Errno 1] _ssl.c:510

问题 I ran into the recent Authorize.net SSL certificate invalidation debacle last week. I've been able to get curl to accept their certificate finally: $ curl -Iv https://secure.authorize.net ... * SSL certificate verify ok. ... but python is still rejecting it with requests: >>> requests.get('https://secure.authorize.net', verify=True) ... InsecurePlatformWarning and in my code: File "/usr/lib/python2.7/ssl.py", line 405, in do_handshake self._sslobj.do_handshake() SSLError: [Errno 1] _ssl.c:510

问题 getHostedPaymentPageRequest only provides two types of transaction to generate a token for the form using the following XML. Two transaction type: authCaptureTransaction authOnlyTransaction <getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd"> <merchantAuthentication> <name>5KP3u95bQpv</name> <transactionKey>346HZ32z3fP4hTG2</transactionKey> </merchantAuthentication> <transactionRequest> <transactionType>authCaptureTransaction</transactionType> <amount>20.00</amount>

问题 getHostedPaymentPageRequest only provides two types of transaction to generate a token for the form using the following XML. Two transaction type: authCaptureTransaction authOnlyTransaction <getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd"> <merchantAuthentication> <name>5KP3u95bQpv</name> <transactionKey>346HZ32z3fP4hTG2</transactionKey> </merchantAuthentication> <transactionRequest> <transactionType>authCaptureTransaction</transactionType> <amount>20.00</amount>

问题 We are going to build a mobile app for iOS and Android (might build a web app later) where users can upload videos and their friends and followers can watch them. The videos can be either free or also be tagged with a price. If I tag a video with $1 when uploading it, my friends and followers will have to first pay $1 to watch and after paying that $1 they can watch it any time after that. My client wants to use Authorize.net to do the payments. In iOS there are restrictions like we must use

问题 We are going to build a mobile app for iOS and Android (might build a web app later) where users can upload videos and their friends and followers can watch them. The videos can be either free or also be tagged with a price. If I tag a video with $1 when uploading it, my friends and followers will have to first pay $1 to watch and after paying that $1 they can watch it any time after that. My client wants to use Authorize.net to do the payments. In iOS there are restrictions like we must use

问题 We are testing with SOAP against the test url - https://apitest.authorize.net/soap/v1/Service.asmx Curious if this is the Sandbox environment with TLS 1.0 and 1.1 disabled? 回答1: From an email from Authorize.Net last year: Dear Authorize.Net Partner: As you may be aware, new PCI DSS requirements state that all payment systems must disable early TLS by 2018. In preparation for this requirement, Authorize.Net plans to disable TLS 1.0 and TLS 1.1 on the following dates: Sandbox: April 30, 2017