jaraco / jaraco/world

Blue Apron - Order cancelled due to broken payment system

Open
#1 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

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?

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

Domain
payments
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.