Wondering if anyone has any info regarding CyberSource...
What I am trying to accomplish is a SOAP request to perform an inquiry.
Looking for any documentation and/or examples on how to perform a SOAP request using either the merchantReferenceCode or preferably the requestToken or requestID to check the status of the transaction.
Thanks I really appreciate it!
Related
I'm trying to implement 3D Secure via CyberSource's REST API. I've got their REST SDK via : Github REST SDK and I've been using their Live Console examples as well: CyberSource Live Console
Now I know you meant to start by setting up Payer Auth via
On this link: Setup Payer API Ref
But want I'm looking for is a guide on how all the parts are put together, all their other older implementations seem to have PDF guides demonstrating the different flows of the API but I can't find anything for REST. I know at the end I should using the example of "Authorization with Payer Auth Validation" via this link Payer Auth API Ref but I need to be able to test everything, and know what properties I need to use on which API call or share between API calls.
For instance like this 3D Secure API guide: Sage Pay API Guide . On this guide they detail the various request and response messages. Different flows, such as Frictionless authentication , Challenge Auth. I'm specifically interest in the Challenge Auth flow whereby you would redirect your customer to the acsUrl received. If anyone has any guides or assistance they can provide to make this process more clear it would be greatly appreciated. We've put in requests for more information from the intermediary party we are using between CyberSource but it's slow going. Thanx all
For anyone else arriving here, there is now a CyberSource 3D-Secure REST guide here.
At this time there is not a guide for the REST API that has the complete picture. Instead you have to use the SOAP API guide here SOAP Guide. See Chapter 2 within that guide. Where that guide references SOAP API calls replace them with the REST API calls. It's not ideal but that is all that is available.
I am having trouble naming rest endpoints for my otp service.
Here I have 4 endpoints, in brackets I have given inputs
SEND API (Mo. No.) - Generates OTP and send to mobile number, in response it gives TransactionId
RESEND API (TransId) - Resend same OTP to mobile Number with the transactionId
VERIFY API (OTP, TransId)- Verify if the OTP given for the transactionId, is correct to what is stored in cache
ISVERIFIED API (TransId) - Check whether particular transactionId is verified or not
Can anyone please tell me how should I make REST endpoints for these APIs, adhere-ring to REST principles of resources, etc.
I thought of
POST v1/sendOTP
POST v1/resendOTP
POST v1/verifyOTP
POST v1/isVerifiedTransaction
Obviously, this is not a good design of endpoints, I need some help
Better approach would be
POST v1/send-otp
POST v1/resend-otp
POST v1/verify-otp
POST v1/is-verified-transaction if you have to make the separate endpoint for each
else as these can be part of the same end-point only the payload can be different, you cna do something like
POST v1/otp?action=send
POST v1/otp?action=re-send
POST v1/otp?action=verify
POST v1/is-verified-transaction or v1/transaction?status=is-verified
Maybe you should have otp and transaction as resources and do something like this:
POST v1/otp/send
POST v1/transaction/{transId}/resend
GET v1/transaction/{transactionId}/verify?otp={otpId}
GET v1/transaction/{trandId}/isVerified
I am not sure how otp and transactions relate, so it might be a bit off, just throwing the idea of having them as resources
I'm trying to found out how to send a REST request to WSO2's publisher to create a new API without out having to utilize the UI at all. Can anyone help point me in the right directions as to how to start to do this?
Thank you
You can find Publisher REST API docs here.
https://docs.wso2.com/display/AM210/apidocs/publisher/index.html#guide
Business Catalyst has a push notification for new customer inquiries that sends a POST request with the object ID, e.g.ObjectID=1234567&ObjectType=2001
The answer to this question say to use the SOAP API(Legacy) to request the details of the case.
Is there a way to do this using the new Rest API?https://docs.worldsecuresystems.com/reference/rest-apis/index.html
There is no documented method for a cases or case endpoint.
If not, the only solution wil be to mix the API calls being used .
Some of the API's haven't been updated to v3 yet (REST) so unfortunately you will still need to use the SOAP endpoint for the Cases API.
Seeing lots of un-answered Docusign questions, but I'll take the chance anyway.
I see lots of examples of how you can use the returnURL parameter using the Docusign REST api in order to redirect a user to a custom URL upon completion of signing. For example: How to redirect to back after signing completion in docuSign
Nowhere can I find a similar setting when using the Docusign SOAP API. Perhaps someone out in the stack universe knows more? Maybe someone is a better googler than I?
It will always be found in the RequestToken, whether it's for sender, recipient, correct, etc. Info here