You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Second entry should be for `CyberSource_SJC_US` certificate with alias name as CyberSource_SJC_US
175
175
176
176
## PoolingHttpClient
177
-
5
177
+
PoolingHttpClient is built using the apache's PoolingHttpClientConnectionManager class. It comes with retry functionality which is very much needed in case if
178
+
SDK receives an I/O error/exception, when executing a request over a connection that has been closed at the server side. However there might be some cases when
179
+
transaction has reached server and similar or some other exception has occurred. We are considering `merchantTransactionIdentifier` as idempotent key, specially
180
+
in case of auth service(`ccAuthService`). Hence if you want to use PoolingHttpClient, for auth service(`ccAuthService`) merchantTransactionIdentifier field is
181
+
mandatory in the payload for both nvp and xml. The value of the merchant transaction ID must be unique for 60 days.
182
+
183
+
To get more information related to connection pooling please refer wiki.
178
184
179
185
## Message Level Encryption
180
186
CyberSource supports Message Level Encryption (MLE) for Simple Order API. Message level encryption conforms to the SOAP Security 1.0 specification published by the OASIS standards group.
0 commit comments