All have failed on the second payment of the subscription

To date, there has not been a single case of a second successful subscription payment.
The number of failed cases is about to reach 20.
I find this a bit unnatural.
It is unlikely that all of them were caused by the user’s card information.
Immediately after the failure, the card information is deleted and no details are available.
Is there any way to find out why they failed?

The number of failed payments is about to reach another 30 cases.
This is clearly a glitch on square’s part.
It is a fatal glitch. If this is not remedied I will go broke.

Do you have an example failed payment or subscription_id that has the failed payments? :slightly_smiling_face:

Example.
subscription_id

d4668a6a-6894-433b-896b-a851bb7c1720
b2429fc0-d2ab-4cce-9167-b5a1ab6dd058
08e9272c-4dd5-4251-8362-62de75a4c170
e7d68b35-8e9d-41c1-93a3-42f5e1dc28d8
05a525fa-54d9-4826-8d42-bc01c8998ff5
67ec7fd7-f706-4acf-b9a4-0e7e686491dc
611fca47-6c1e-44c4-b228-f75cec11a880
d5fc6c55-9218-43a3-8980-d878a7ed846e
73b36028-d000-4756-a818-46778a12f530
f0fa4780-5403-42c4-96d2-a7c97d11402c
af8c4d2f-5197-4d42-b198-ce37d82f776a
baeb39d7-88b7-4a1f-ada3-3e4c8be9da20
16ede20a-c3fc-4be3-956e-a38552d236cb
861d0ea8-4b06-49da-a725-b3c8f3bf07dd
4b8dd194-c1c6-46f6-ae92-88f502432fa6
8fdc9968-ea76-4cbb-b4cd-0a2720380090
50f0b19f-9b9e-4b1b-9a4e-1d6cd456798e
792e1262-bd92-4905-b8da-535bd59b825a
732b10ec-17f0-49d1-a043-1d58c4fb683a
899a1f7c-6b86-40bd-9d4d-6411a7781723
943a8e96-8deb-4840-a22f-139a3df516ae
81a8b51d-008c-4779-9541-54067de7bcbe
fd2da026-2973-4afc-a252-d42cac110c36
f426df05-b3bc-468e-9564-45aac85bde99
c17cc6cf-658d-4f24-a5eb-c621719a449f
f3860808-1871-4789-87d4-61116d5897bf
eee3eff5-4840-4df3-9c6d-76f29149e259
4c7aa040-0c22-4a11-930f-f47492952080

Add.

subscription_id
dd05ac53-5dcb-4b63-91c8-622f04815d2f
49793b09-60d3-4905-ae7e-6a0e76c53dfe
340822e7-6bee-4cd3-a082-4357379b9e84
221b969e-1127-4c6c-87ef-be758a5326f3
b27aab0a-d2a8-49ca-90d2-12df8ad3172b
2c131852-b24d-49e6-b6b7-b0b1f8f8c3eb
85a78b85-15b8-4030-a338-46440da92ad6
5257a08e-8cff-4013-ad9e-137884527f30
391874d5-1956-4fdd-84b9-c16393506f09
558b5a46-3a3e-4eb5-8095-dd6a4f480434

There are no subscriptions that have been successfully paid a second time to date.
Is this case under investigation?
I would like a reply.

I spot checked 6 of those subscriptions and they all have a second payment. For example subscription dd05ac53-5dcb-4b63-91c8-622f04815d2f has two invoices which are:

  • inv:0-ChB1YUZdls24Il6d7xf0g_fNEN4K
  • inv:0-ChCufv1quIYOo5uj2lwAfFtqEN4K

Both are paid for. :slightly_smiling_face:

The second submission was paid from an invoice the user received via email.
For example.

dd05ac53-5dcb-4b63-91c8-622f04815d2f

is displayed in dashbord as a failed payment with a stored card.
This user made a second payment, but the user information shows no stored card.
There is not a single subscription that has been successfully paid with a saved card.

Please check the subscription id in my first post. Not a single subscription has been successfully paid by a stored card.

Looking at the API logs I see the a call to DisableCard was made for the customer of the subscription. Was that intentional? :slightly_smiling_face:

DisableCard is not done intentionally.
It was not erased by the user because the card information remains locally.
I checked the dashboard and the card information is stored for users who created subscriptions within a few days.
However, it now appears that users who created subscriptions before 2/28 do not have their card information saved.

But there’s a call from your application to DisableCard. How is that being called? :slightly_smiling_face:

I am using the python square library.
When the user deletes the card information, DisableCard is called and the local card information is also deleted.
Just to confirm, can a user remove card information from an email invoice?

Yes, they can remove a card from the invoice. Customers have to have access to remove their card on file. :slightly_smiling_face: