Blue Apron - Order cancelled due to broken payment system
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 10/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- payments
Research direction
The report names Blue Apron, order B4797182, Apple Pay, and a second credit card, but provides no repository files, tests, or entry point. First determine whether this repository contains the affected payment and order system and obtain a reproducible failure. Done would require a defined fix for payment retries, payment-method handling, and cancellation behavior, with tests.
Written by the indexing model from the issue text.
Description
Yesterday, I spent over an hour trying to figure out why Blue Apron was unable to accept payment for order B4797182. Sadly, my support agent and her supervisor were unable to help. They insisted that there was no way to re-attempt the payment or fix the Apple Pay issue. I was informed that the only thing we could do was wait for the second payment attempt. There appears to be no way to delete the Apple Pay payment method (or recreate it). Since I was not confident that the second payment attempt would work, I volunteered to add a second payment method to ensure that the order would be processed. The supervisor agreed that would be the safest way to ensure our order would be placed. Sadly, BA screwed up again, and despite the supervisor’s assurance, the Apple Pay charge did not go through. But worse, despite the supervisor’s assurance, the additional credit card I added was not charged and instead the order was cancelled by a heartless machine in the middle of the night.
WE ARE SO ANGRY!!!
We bent over backwards to try to work around the limitations of YOUR BROKEN SYSTEM, and we still were unsuccessful. Your support agents are either incompetent or they’re rendered so by the limitations of your system.
And the consequences fall on us to plan and procure meals for next week.
How are you going to fix this situation?
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jaraco/world
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 1/5 Under an hour Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
VelaPayments/vela-payments#168 ·
-
complexity complexity: low Drips frontend security testing ui
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opencollective/opencollective#9120 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area: indexer bug complexity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
accensa/accensa-app#815 ·
Maintainers usually reply within 1 day