Hi, we have a merchant partner that utilizes draft orders. Our payment extension works for regular customer initiated orders on their web storefront, but when they provide a draft order to their customer and try to select our payment extension at check out we receive this error message :
”There was an issue processing your payment. Try again or use a different payment method.”
We aren’t receiving any calls to our extension so we are unable to tell if it is an issue on our application payment extension or if it is an error on Shopify’s end.
Hey @Michelle_Lamoureux happy to look into this for sure. If you’re able to replicate the issue on your end, could you pull an x-request-id value from the headers for an example error response payload if possible? It should be accesible here in your CHrome Dev Tools:
Thanks @Michelle_Lamoureux - appreciate you grabbing that ID. I was able to pull some logs on our end and the internal error message I’m seeing appears to be related to delivery methods. This does seem odd to me, so I’m going to reach out to some folks internally on my end to investigate further. I’ll keep you up to date in this thread as soon as I have more to share - thanks again for sharing the request ID, it helps a lot!
Hey Alan, we actually were able to resolve yesterday. I was working with Danny Elisha and he was able to support us finding that we were having errors coming through as it related to the phone number.
It was an interesting scenario, for the draft orders and how Shopify passes the customer identifier number when it is placed in a draft order, it comes to use with the + and space characters, whereas the traditional online order Shopify filters out the space and + characters.
Our phone number validation service was not accepting the space or + characters so we lifted some of our restrictions to ignore those character types and we were able to successfully connect to our payment extention.
Thanks for following up @Michelle_Lamoureux, definitely very interesting. I’m guessing that could have been what prevented the delivery method from populating as well. Glad it’s all fixed though, let me know if I can help out any further on my end
happy to look into this for sure. If you’re able to replicate the issue on your end, could you pull an 
