Hi, I'm using a sandbox environment and I'm trying to generate a payment using an existing token, but am getting a 403 error. I tried the following things.
First, I have generated a REST Shared Secret key, and using both HTTP Signature as well as a p12 certificate, my calls to https://developer.cybersource.com/api-reference-assets/index.html#transaction-search_search-transact... seem to work either way. I've even been able to generate payments with a credit card.
I manually generated a subscription within the ebc2test admin UI. No issues... it gives me a valid customer number to work with, does the charges correctly, etc.
Now to the API endpoints I may want to use. I decided to start with a simple "Get a subscription" https://developer.cybersource.com/api-reference-assets/index.html#recurring-billing-subscriptions_su... since nothing else seemed to be working. I changed the parameter correctly to have the correct subscription number i.e. https://apitest.cybersource.com/rbs/v1/subscriptions/6XXXXXXXXXXXXXXXXXXXX2 (obscured here) and I get the following response:
{
"submitTimeUtc": "2023-04-30T06:17:25.755Z",
"status": "FORBIDDEN",
"reason": "INVALID_DATA",
"message": "Authorization Failure!",
"details": []
}
What I don't get is why some endpoints seem to get a 403 and some don't with the exact same values for authorization. Any ideas?
04-29-2023 11:19 PM
For anyone following this thread, I have emailed their developer support using this form https://developer.cybersource.com/support/contact-us.html and will post a follow-up presuming something useful comes back from them.
05-09-2023 12:33 PM