Forum | Appery.io

Hi Jon -

We are sorry for silence here, our developers team are currently investigating this issues with Stripe API integration in Appery.io.

If you want to get a faster responses to your issues, please use our mail support channel.

Thank you Illya, I will start using the priority support, but a couple of times I received absolutely no response from there as well (which is even worse).

Jon - if so, we need investigate the cause of this, write us directly to: a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a - when you've used priority support and which email address were used.

Hello,

Replied here https://getsatisfaction.com/apperyio/...

Thank you Alena, but that response is irrelevant to this issue. The Request Content Type has always been x-www-form-urlencoded... The API key has always been correct. Proxy still doesn't work unless you hard-code the API key into the Authorization field...

Please see my original post.

Stripe services do not work if you don't put "Bearer sk_ahsdyt985yethriudf" in the Authorization field. Using "Bearer {api_key_proxy}" does NOT work. The problem is with the setup of the proxy service...

Maybe in your response on the other thread you meant to address the other problem (testing the cardToken service from the Test tab in the builder). But that's a secondary problem (and it still doesn't work). I still don't know whether I should delete the stripe services and recreate them (and I'd have to redo all of the mapping for those services on all pages).. But this is the major issue (not being able to use the proxy service).

We figured it out.

Inside the StripeDB "Credentials" collection for the proxy, we made the keyValue for the "api_key_proxy" equal to "Bearer sk_XXXXXXXXXX" and use only {api_key_proxy} in the authorization header field (so the word "Bearer" is being carried over during the proxy service)... This worked and the Stripe service no longer requires hard-coding the stripe API key onto the client's device...

Thanks for the help guys. Sorry about the inconvenience.

Thank you for update, Jon

Thank you for update, Jon

Its my first time using Secure Proxy and I am having this same issue for Push Notifications. Seems simple, but does not work. How did you solve it?

I get the following error message.

{
"status":404,
"uri":"https://api.appery.io/rest/push/msg",
"response":{
"code":"PNMN004",
"description":"Push API Key: {PushAPIkey} not found"
}
}

I have setup database and the key correctly