You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 16, 2021. It is now read-only.
Hi, this is probably the wrong module, but I can find anyplace to post issues for the coinbase commerce stack and the main support channels seem to have a months-long backlog.
Coinbase commerce works OK, but has one basic UI issue: it doesn't allow setting of the icon when creating a charge that is not made from a checkout.
This makes the UI for the hosted solution look broken.
Request: support some form of setting the image when directly creating a charge, much the way it is supported today when creating a checkout.
(We can't use a checkout because there's no support there for extended metadata :-( It has a "requested_info" field, but there are only two possible values. In particular, there's no way to collect an invoice number of similar, making it hard to use for linking to actual charges in commerce. So, both avenues have led to a dead end and there appears to be little-to-no connection to the tech team via the standard support channels. Can you suggest a way to give this to the right team?)
The text was updated successfully, but these errors were encountered:
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
Hi, this is probably the wrong module, but I can find anyplace to post issues for the coinbase commerce stack and the main support channels seem to have a months-long backlog.
Coinbase commerce works OK, but has one basic UI issue: it doesn't allow setting of the icon when creating a charge that is not made from a checkout.
This makes the UI for the hosted solution look broken.
Request: support some form of setting the image when directly creating a charge, much the way it is supported today when creating a checkout.
(We can't use a checkout because there's no support there for extended metadata :-( It has a "requested_info" field, but there are only two possible values. In particular, there's no way to collect an invoice number of similar, making it hard to use for linking to actual charges in commerce. So, both avenues have led to a dead end and there appears to be little-to-no connection to the tech team via the standard support channels. Can you suggest a way to give this to the right team?)
The text was updated successfully, but these errors were encountered: