Home › Forums › Stripe Payments Plugin › Subscription update seems to give wrong description to single paymen
- This topic has 5 replies, 2 voices, and was last updated 3 years, 8 months ago by [email protected].
-
AuthorPosts
-
February 8, 2021 at 8:06 am #3605[email protected]Participant
Hi guys,
We super appreciate the update that sends installments description to Stripe. Unfortunately though it just happened that a “normal” single payment got a mixed up description delivered to Stripe, see screenshot below.
See the product name in the metadata has the correct description, in the Payment details though it claims to be an installment for a entirely different, subscription type product.
Any ideas? Thanks!
February 9, 2021 at 1:00 am #3606AdminKeymasterCan you please download the version from the following page for the main Stripe plugin and use that?
Do you see the issue with it? I tested with that version and I am not seeing the issue. My description for the one time payment product’s has the correct value that I set in the “Short Description” field of the product configuration. I also tested without putting a short description value in which case, it correctly puts the product’s name in the description.
You are creating separate products for Subscription products and one time products correct? I mean you are not trying to re-use one subscription product and re-purpose it for a one time payment product.
February 9, 2021 at 9:28 am #3607[email protected]ParticipantHi, I used the test version and made a few test requests, trying both with and without a short description for the product (which is a normal separate, single product yes): Still incorrect, and at the same time I also realized that it affects (single) payments coming to the API from another application (ie. not from WordPress). That seems more than surprising, so now I am thinking of invoking Stripe support.
Subscription update payments (also from the other app) are coming through correctly btw. And interestingly, those don’t update that “wrong” description (see below) that is being used, this one is just stuck.
In the object you see a mix of the correct description (Summit – Hawaii In-Person Option) and the incorrect description (Summit – Payment Plan 3 (4x USD 277.50) (2 of 0))
{ "id": "", "object": "payment_intent", "last_payment_error": null, "livemode": false, "next_action": null, "status": "succeeded", "amount": 33300, "amount_capturable": 0, "amount_received": 33300, "application": null, "application_fee_amount": null, "canceled_at": null, "cancellation_reason": null, "capture_method": "automatic", "charges": { "object": "list", "data": [ { "id": "", "object": "charge", "amount": 33300, "amount_captured": 33300, "amount_refunded": 0, "application": null, "application_fee": null, "application_fee_amount": null, "balance_transaction": "", "billing_details": { "address": { "city": "", "country": "AT", "line1": "", "line2": null, "postal_code": "1234", "state": "" }, "email": null, "name": "", "phone": null }, "calculated_statement_descriptor": "ASCENSION ONE", "captured": true, "created": 1612861937, "currency": "usd", "customer": "", "description": "Summit – Payment Plan 3 (4x USD 277.50) (2 of 0)", "destination": null, "dispute": null, "disputed": false, "failure_code": null, "failure_message": null, "fraud_details": { }, "invoice": null, "livemode": false, "metadata": { "Product Name": "Summit - Hawaii In-Person Option", "Product ID": "20523" }, "on_behalf_of": null, "order": null, "outcome": { "network_status": "approved_by_network", "reason": null, "risk_level": "normal", "risk_score": 25, "seller_message": "Payment complete.", "type": "authorized" }, "paid": true, "payment_intent": "", "payment_method": "", "payment_method_details": { "card": { "brand": "visa", "checks": { "address_line1_check": "pass", "address_postal_code_check": "pass", "cvc_check": "pass" }, "country": "US", "exp_month": 4, "exp_year": 2022, "fingerprint": "", "funding": "credit", "installments": null, "last4": "4242", "network": "visa", "three_d_secure": null, "wallet": null }, "type": "card" }, "receipt_email": "", "receipt_number": null, "receipt_url": "", "refunded": false, "refunds": { "object": "list", "data": [ ], "has_more": false, "total_count": 0, "url": "" }, "review": null, "shipping": null, "source": null, "source_transfer": null, "statement_descriptor": null, "statement_descriptor_suffix": null, "status": "succeeded", "transfer_data": null, "transfer_group": null } ], "has_more": false, "total_count": 1, "url": "" }, "client_secret": "", "confirmation_method": "manual", "created": 1612861934, "currency": "usd", "customer": "", "description": "Summit – Payment Plan 3 (4x USD 277.50) (2 of 0)", "invoice": null, "metadata": { "Product Name": "Summit - Hawaii In-Person Option", "Product ID": "20523" }, "on_behalf_of": null, "payment_method": "", "payment_method_options": { "card": { "installments": null, "network": null, "request_three_d_secure": "automatic" } }, "payment_method_types": [ "card" ], "receipt_email": "", "review": null, "setup_future_usage": "off_session", "shipping": null, "source": null, "statement_descriptor": null, "statement_descriptor_suffix": null, "transfer_data": null, "transfer_group": null }
(Ids and personal data are removed from the object.)
February 9, 2021 at 9:54 am #3608[email protected]ParticipantSome additional info: I checked on the events log for payments from that other non-Wordpress application, and the log tells me that it was initially received with the correct description (coming from their app), and this was followed by an additional request, updating it to the wrong description (coming from WordPress):
Source Stripe/v1 PhpBindings/7.28.1 Stripe Payments/2.0.43 (https://wordpress.org/plugins/stripe-payments/)
POST /v1/payment_intents/pi_xxx
200 OK
View log detail
Request parameters
{
“description”: “Summit – Payment Plan 2 (3x USD 370.-) (2 of 3)”
}So it seems that the plugin on WP is doing “rogue updates”? Btw. is there a link to the previous version of the plugin?
February 10, 2021 at 11:25 pm #3614AdminKeymasterPlease update the subscription addon to v2.0.30. That should resolved this issue.
February 12, 2021 at 10:58 am #3621[email protected]ParticipantTHANK YOU, looks good! <3
-
AuthorPosts
- You must be logged in to reply to this topic.