Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connections.Response Overloading and In Skill Purchasing. #10

Closed
aadupirn opened this issue Oct 1, 2019 · 1 comment
Closed

Connections.Response Overloading and In Skill Purchasing. #10

aadupirn opened this issue Oct 1, 2019 · 1 comment

Comments

@aadupirn
Copy link

aadupirn commented Oct 1, 2019

The response type "Connections.Response" is used in a lot more places than In Skill Purchasing. For the alexa amzonpay integration its used for a couple different requests. The API docs are here. The responses that alexa makes to the Setup and Charge steps are both using Connections.Response. I'm adding models following this pattern for an amazonpay-alexa integration and am happy to pr them here though I'm not sure if this is the right repo for them. Is this project just intended for in app purchasing and such or all alexa purchasing integrations? The name makes it a little unclear to me.

@stoiveyp
Copy link
Owner

stoiveyp commented Oct 1, 2019

Hi @aadupirn - Amazon Pay and In-Skill Purchasing are different enough that I don't feel putting them into the same repo is desirable. It is a shame that there's re-use of some of the object type identifiers, but I still think it would be better for skill developers to keep them separate.

Initially I left this particular journey out of the support I wrote with all the Alexa.NET extensions as the process required becoming an Amazon Pay merchant - which wasn't something I was prepared to do, but it would be great if you were able to provide that for our users.

Thanks for your enquiry - let me know if there's anything else I can help with

Steven

@stoiveyp stoiveyp closed this as completed Oct 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants