netaxept payment integration in interspire throw Refused by issuer Exception - soap-client

i am integrating netaxept payment gateway in interspire shopping cart but its throwing exception "Refused by issuer" each time i try to porocess the folling line
$OutputParametersOfProcess = $client->__call('Process', array("parameters" => $InputParametersOfProcess));
this is working in sample code but not working for me the only difference i have notice that tha SoapClient sdl Resource id #10 with the sample code and for me is 68 or 69
i am unable to figure out the problem either with SoapClient library or with the service provider.

There should be more info in the return value. Refused by issuer really means that the bank declined your payment.

Related

Problem with Wallet Creation, signature error

I want to create a wallet for new rest api server, but whenever I call code to generate new Wallet I'm getting error like
"Decoding SignatureHeader failed: Error illegal buffer ..."
Here is screen shot of my code, it is taken from virtual machine
I'm using hyperledger fabric 2.2 and run under the fabric-samples/test-network
I was clone this HyperledgerFabroc
Here is also print screen of the error:
I would appreciate if someone can navigate me how to manage successfully to create a wallet ?
Your error looks to be occurring within a chaincode transaction function. You should not be using the client SDK to do a transaction invocation from within chaincode. Instead look to use the invokeChaincode function on the stub:
https://hyperledger.github.io/fabric-chaincode-node/release-1.4/api/fabric-shim.ChaincodeStub.html#invokeChaincode

Exception: 401 Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential

I've seen a few people over the years facing similar issue but I haven't found much regarding my case.
I have a backend built with python3.
I am using firebase_admin as a library to connect to Firebase Cloud Firestore.
I then commit my code to Github and using Github Actions
I am deploying the docker container to Google Cloud Run.
This all works fine for some time
Some time later throws the following exception: Exception: 401 Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
What am I doing wrong?
Should I connect every time I call the function? (move the db initialization in each function call)
Feels like the token expired. Can I refresh it somehow?
Python code:
from firebase_admin import firestore, initialize_app
initialize_app()
db = firestore.client()
def get_info_from_firestore(name: str:
try:
data = db.collection(u'data').where(u'title', u'==', name).stream()
for rating in ratings:
return rating.to_dict()
return None
except Exception as e:
logging.warning(Exception: {e}')
return None
And this file is imported from my root python file that's using Flask.
Edit: One final thing that might help, if I redeploy my container without any changes it all works again.
Likely this is happening due to time drift: time in docker significatly differs realtime. After restart time is in sync but after a while it drifts. Google does not like it. See more info about this WSL/container issue here https://github.com/microsoft/WSL/issues/4245 and here https://github.com/docker/for-win/issues/4526

Job schedule entry could not be created. Status code: 500

I have received the following error when trying to save a DSX Scheduled Job:
Job schedule entry could not be created. Status code: 500
Screenshot of the error message:
I've tried about six times over the last few hours and have consistently received the above error message.
Debugging via the browser network inspection tool I can see:
{
"code":"CDSX.N.1001",
"message":"The service is not responding, try again later.",
"description":"",
"httpMethod":"POST",
"url":"https://batch-schedule-prod.spark.bluemix.net:12100/schedules",
"qs":"",
"body":"While attempting to get Bluemix Token from BlueIDToken, unable to retrieve AccessToken, failed with status 400 Bad Request, message = {\"error\":\"invalid_grant\",\"error_description\":\"A redirect_uri can only be used by implicit or authorization_code grant types.\"} Entity: {\"error\":\"invalid_grant\",\"error_description\":\"A redirect_uri can only be used by implicit or authorization_code grant types.\"}",
"statusCode":500,
"duration":666,
"expectedStatusCode":201
}
As per Charles comment, the functionality is working ok now. I guess if this happens to another user some time in the future they should contact support.

org.apache.axis2.AxisFault: Transport error: 411 Error: Length Required (CloudConnect Salesforce sample ETL SOQL validation error)

SOQLvalidation threw validation error in CloudConnect Salesforce sample ETL.
org.apache.axis2.AxisFault: Transport error: 411 Error: Length Required
Data retrieve target Salesforce organization uses custom domain.
I would like to know what caused above error and how to resolve.
This is the known issue (bug) in CloudConnect. We are working hard to fix this.

Padding is invalid and cannot be removed while sending push event to my application

We are using Docusign Connect to leverage the push functionality. This feature is great and we are no more worried of reaching REST call limits.
But while checking connect logs on DocuSign console- We found failure entry which is failing because of below error:
9/16/2013 6:50:23 AM Connect send to: https://myURL.com/EventListener
9/16/2013 6:50:23 AM Envelope Data (documents were included):
9/16/2013 6:50:23 AM Error: Exception in EnvelopeIntegration.RunIntegration: <EnvelopeID> :: https://myURL.com/EventListener :: Error - Exception decrypting. Padding is invalid and cannot be removed. Original Exception: Padding is invalid and cannot be removed.
Looks like this is some internal exception at Docusign. Can someone help us to resolve this issue?
This is indeed a bug on DocuSign's side. It's newly introduced which means it most likely came from the latest release. Will post an update here once resolved, thanks for your patience.
DocuSign Team

Resources