pull down to refresh

I ordered something and paid (lightning transaction successful), and it said "thank you, order has been received, order number : 3148".
But then it said "there has been a critical error on this website." I also didn't get a confirmation email or anything.
Can you check if there has been any problems?
0 sats \ 4 replies \ @sox 20 Mar
I thought it was just a WordPress error about some plugin, yesterday I did an order too ^^ 3146
reply
174 sats \ 0 replies \ @AG 20 Mar
Yes indeed, it was probably a wp error, I'll try to replicate and hopefully we'll fix it as soon as possible. Your order has been successfully processed and your item is on the way ;)
reply
100 sats \ 2 replies \ @AG 20 Mar
your order delivery date is Tuesday, April 1. Hope it's ok! We are working with shipping providers to have faster shipping times in the future. We'll add a small gift for you to compensate :)
reply
21 sats \ 1 reply \ @sox 20 Mar
A delivery on April Fools? That’s so cool omg
reply
0 sats \ 0 replies \ @AG 20 Mar
yes, it coincides. Is not a joke though 🤣
reply
0 sats \ 4 replies \ @AG 20 Mar
Weird, other orders have been successfully processed and items are being shipped. Your order has been received but look not paid in our side. Which payment method did you select? Can you double-check in your lighting wallet if the transaction went out?
reply
I think it was paid by Speed.
I see the lightning payment in my wallet... 73,046 sats. Do you need any details to help troubleshoot?
reply
0 sats \ 1 reply \ @AG 20 Mar
Ok, that's all good :) The error is due to our partners' integration as we have some delays on order approvals. That's why WP provide an error and the order stay on pending status. Anyway, your order is now in production and should be delivered by Friday, March 28.
Thank you for your patience, a small gift has been added to the parcel for you!
reply
Thanks for resolving it quickly!
reply
0 sats \ 0 replies \ @AG 20 Mar
Yes it was Speed. I can confirm the payment has been received, I'll process your order manually. Thank you for reporting this bug. We'll investigate more on this bug.
reply