Stripe issueshttps://lab.civicrm.org/extensions/stripe/-/issues2024-03-25T20:04:28Zhttps://lab.civicrm.org/extensions/stripe/-/issues/473Drupal 9 + WebForm: "Bad Request" after upgrading to CiviCRM 5.71.02024-03-25T20:04:28ZmasettoDrupal 9 + WebForm: "Bad Request" after upgrading to CiviCRM 5.71.0I don't know if this is a Stripe or Firewall issue, I write what happened to me.
I have a CiviCRM installation with Drupal 9.5.11 and WebForm 6.2.4. After upgrading to CiviCRM 5.71.0 (I had the same problem on v5.70.0), the webform conn...I don't know if this is a Stripe or Firewall issue, I write what happened to me.
I have a CiviCRM installation with Drupal 9.5.11 and WebForm 6.2.4. After upgrading to CiviCRM 5.71.0 (I had the same problem on v5.70.0), the webform connected with Stripe payment processor give me an error
![image](/uploads/fb6448037d868c3d01be677fec1b1d14/image.png)
I debugged and found that the error is generated in `Civi/Api4/Action/StripePaymentintent/ProcessPublic.php`:
```php
$event = \Civi::dispatcher()->dispatch('civi.stripe.authorize', $authorizeEvent);`
if ($event->isAuthorized() === FALSE) {
throw new \CRM_Core_Exception('Bad Request');
}
```
The API4 is `StripePaymentintent.ProcessPublic` and these are the parameters:
```
Array
(
[paymentMethodID] => pm_1OrhO7GYnf18AbeR11Ftobfo
[amount] => 4.00
[currency] => EUR
[paymentProcessorID] => 3
[description] => Donate Now
[extraData] =>
[csrfToken] => 1709820194.b23530a1ab275ce872a9271d.3454a517e3658a9bbf1e380ec4a9228d49d0c618efaa7fb13dbfc41e860f7445
[captcha] =>
[checkPermissions] => 1
)
```
My IP finished in `civicrm_firewall_ipaddress` table, event_type "InvalidCSRFEvent" and source "tampered hash".
Sorry if I wrote in the wrong place, but I don't know how to untangle myself to understand and fix it.https://lab.civicrm.org/extensions/stripe/-/issues/472Merchant code settings2024-03-09T12:59:55ZlcarterMerchant code settingsA client has asked about merchant category codes (see https://stripe.com/docs/connect/setting-mcc#mcc-automatic for documentation)... apparently their trxns are coming across as retail even though their code in Stripe is set to College/U...A client has asked about merchant category codes (see https://stripe.com/docs/connect/setting-mcc#mcc-automatic for documentation)... apparently their trxns are coming across as retail even though their code in Stripe is set to College/University. Is this something that's configurable in CiviCRM or is this solely controlled in Stripe itself?https://lab.civicrm.org/extensions/stripe/-/issues/4716.10 - Stripe API 2023-08-16 'and force it to be used', not in all cases2024-02-26T11:35:39ZJKingsnorth6.10 - Stripe API 2023-08-16 'and force it to be used', not in all casesWe've upgraded to 6.10.2 and can see that Stripe API version 2023-08-16 is being used for the majority of requests, but POST requests to `POST /v1/payment_methods` are still going to the 'default' API for the account (which in our case i...We've upgraded to 6.10.2 and can see that Stripe API version 2023-08-16 is being used for the majority of requests, but POST requests to `POST /v1/payment_methods` are still going to the 'default' API for the account (which in our case is 2020-08-27).
This doesn't seem to cause any problems, but just wanted to flag it if we were expecting all API calls to be forced to the latest version, as suggested in the release notes:
> 6.10 release notes: Supports Stripe API version 2023-08-16 (and will force it to be used).
Also, the _latest_ version is 2023-10-16 - but API calls are still going to 2023-08-16.https://lab.civicrm.org/extensions/stripe/-/issues/470CiviCRM 5.70 compatibility (rounding issue) ?2024-03-17T22:49:27ZsamuelsovCiviCRM 5.70 compatibility (rounding issue) ?We have this problem when doing a payment on a contribution page since the upgrade to CiviCRM 5.70 :
![screenshot-20240221](/uploads/d92b4af5dfd8fcd9ed78100dd384f1cc/screenshot-20240221.png)
In our context the total amount is 57.4875 (5...We have this problem when doing a payment on a contribution page since the upgrade to CiviCRM 5.70 :
![screenshot-20240221](/uploads/d92b4af5dfd8fcd9ed78100dd384f1cc/screenshot-20240221.png)
In our context the total amount is 57.4875 (50$ + quebec taxes).
Apparently, Stripe is using Brick which expect some strategy for the rounding.https://lab.civicrm.org/extensions/stripe/-/issues/469Incomplete contribution and Recurring contribution while using stripe_checkou...2024-03-09T13:01:33Zdamo-civiIncomplete contribution and Recurring contribution while using stripe_checkout PPWhen i try to signup for recurring contribution using a contribution page setup with Stripe_checkout as the payment processor, the contribution and its related recurring record are left pending status. Even after running the webhook shed...When i try to signup for recurring contribution using a contribution page setup with Stripe_checkout as the payment processor, the contribution and its related recurring record are left pending status. Even after running the webhook sheduled job the contribution is not completed. Though the payment was taken by stripe.
This happens in CiviCRM v5.69.2 and Stripe v6.10.2https://lab.civicrm.org/extensions/stripe/-/issues/468create_customer - repeated Stripe API errors in CiviCRM log2024-02-09T21:11:40Zrichardsplaygroundcreate_customer - repeated Stripe API errors in CiviCRM logWe are seeing persistent log messages in the CiviCRM ConfigAndLog that look like this:
```plaintext
2024-02-08 22:11:49-0800 [error] Stripe(5): create_customer (unknown error): Stripe\Exception\PermissionException: This API call cannot...We are seeing persistent log messages in the CiviCRM ConfigAndLog that look like this:
```plaintext
2024-02-08 22:11:49-0800 [error] Stripe(5): create_customer (unknown error): Stripe\Exception\PermissionException: This API call cannot be made with a publishable API key. Plea
se use a secret API key. You can find a list of your API keys at https://dashboard.stripe.com/account/apikeys.
2024-02-08 22:11:49-0800 [error] Failed to create Stripe Customer: An error occurred; Array
(
[code] => 9000
[message] => An error occurred
)
```
In the Stripe dashboard I see a lot of these error messages:
![2024-02-09 11.15.49 dashboard.stripe.com 6a5a4a6fecf3.png](/uploads/69b4cb4819f19e92cb812c521917c1ef/2024-02-09_11.15.49_dashboard.stripe.com_6a5a4a6fecf3.png)
These occur every time there is a payment made.
We have checked our API keys and they are correct. Also, the payment does get recorded in both Stripe and Civi correctly.
* Civi 5.68.1
* CiviCRM Stripe 6.10.2
* Stripe API version 2023-08-16https://lab.civicrm.org/extensions/stripe/-/issues/467Subscription that stripe determines is "unpaid" is not updated in CiviCRM to ...2024-03-12T23:30:08ZjamieSubscription that stripe determines is "unpaid" is not updated in CiviCRM to be cancelledIt seems that stripe will send a notice that a subscription is "unpaid" when it gives up trying to collect on it.
I'm wondering if this is a bug or a feature request? I think it's a bug, but if this is not yet implemented let me know. W...It seems that stripe will send a notice that a subscription is "unpaid" when it gives up trying to collect on it.
I'm wondering if this is a bug or a feature request? I think it's a bug, but if this is not yet implemented let me know. We'd be happy to help get this working.
I'm seeing the payment processor web hook reports:
> Payment Processor: Stripe (Live ID: 1)
> Status: This event was successfully processed.
> Identifier: :::sub_xxxxxxx Type: customer.subscription.updated
> Full message:
> doCustomerSubscriptionUpdated: ignoring - not implemented
The JSON data provided by stripe includes:
```
Stripe\StripeObject JSON: {
"object": {
"id": "sub_xxxxxxx",
"object": "subscription",
"application": null,
"application_fee_percent": null,
"automatic_tax": {
"enabled": false,
"liability": null
},
"billing_cycle_anchor": 1626378828,
"billing_cycle_anchor_config": null,
"billing_thresholds": null,
"cancel_at": null,
"cancel_at_period_end": false,
"canceled_at": null,
"cancellation_details": {
"comment": null,
"feedback": null,
"reason": null
},
"collection_method": "charge_automatically",
"created": 1626378828,
"currency": "usd",
"current_period_end": 1708026828,
"current_period_start": 1705348428,
"customer": "cus_xxxxxE",
"days_until_due": null,
"default_payment_method": "pm_xxxxx",
"default_source": null,
"default_tax_rates": [],
"description": null,
"discount": null,
"ended_at": null,
"invoice_settings": {
"account_tax_ids": null,
"issuer": {
"type": "self"
}
},
"items": {
"object": "list",
"data": [
{
"id": "si_xxxxx",
"object": "subscription_item",
"billing_thresholds": null,
"created": 1626378828,
"metadata": [],
"plan": {
"id": "every-1-month-2500-usd",
"object": "plan",
"active": true,
"aggregate_usage": null,
"amount": 2500,
"amount_decimal": "2500",
"billing_scheme": "per_unit",
"created": 1559605475,
"currency": "usd",
"interval": "month",
"interval_count": 1,
"livemode": true,
"metadata": [],
"nickname": null,
"product": "prod_xxxxxx",
"tiers": null,
"tiers_mode": null,
"transform_usage": null,
"trial_period_days": null,
"usage_type": "licensed"
},
"price": {
"id": "every-1-month-2500-usd",
"object": "price",
"active": true,
"billing_scheme": "per_unit",
"created": 1559605475,
"currency": "usd",
"custom_unit_amount": null,
"livemode": true,
"lookup_key": null,
"metadata": [],
"nickname": null,
"product": "prod_xxxxxx",
"recurring": {
"aggregate_usage": null,
"interval": "month",
"interval_count": 1,
"trial_period_days": null,
"usage_type": "licensed"
},
"tax_behavior": "unspecified",
"tiers_mode": null,
"transform_quantity": null,
"type": "recurring",
"unit_amount": 2500,
"unit_amount_decimal": "2500"
},
"quantity": 1,
"subscription": "sub_xxxxx",
"tax_rates": []
}
],
"has_more": false,
"total_count": 1,
"url": "\/v1\/subscription_items?subscription=sub_xxxxxx"
},
"latest_invoice": "in_xxxxx",
"livemode": true,
"metadata": {
"Description": "Join xxxxx Solidarity Circle"
},
"next_pending_invoice_item_invoice": null,
"on_behalf_of": null,
"pause_collection": null,
"payment_settings": {
"payment_method_options": null,
"payment_method_types": null,
"save_default_payment_method": null
},
"pending_invoice_item_interval": null,
"pending_setup_intent": null,
"pending_update": null,
"plan": {
"id": "every-1-month-2500-usd",
"object": "plan",
"active": true,
"aggregate_usage": null,
"amount": 2500,
"amount_decimal": "2500",
"billing_scheme": "per_unit",
"created": 1559605475,
"currency": "usd",
"interval": "month",
"interval_count": 1,
"livemode": true,
"metadata": [],
"nickname": null,
"product": "prod_xxxxx",
"tiers": null,
"tiers_mode": null,
"transform_usage": null,
"trial_period_days": null,
"usage_type": "licensed"
},
"quantity": 1,
"schedule": null,
"start_date": 1626378828,
"status": "unpaid",
"tax_percent": null,
"test_clock": null,
"transfer_data": null,
"trial_end": null,
"trial_settings": {
"end_behavior": {
"missing_payment_method": "create_invoice"
}
},
"trial_start": null
},
"previous_attributes": {
"status": "past_due"
}
}
```https://lab.civicrm.org/extensions/stripe/-/issues/466Update test api keys?2024-01-24T10:33:20ZjitendraUpdate test api keys?Seems like test api keys https://lab.civicrm.org/extensions/stripe/-/blob/master/tests/phpunit/CRM/Stripe/BaseTest.php#L143 are expired?
Test failing reported at https://github.com/colemanw/webform_civicrm/pull/939#issuecomment-1906200328Seems like test api keys https://lab.civicrm.org/extensions/stripe/-/blob/master/tests/phpunit/CRM/Stripe/BaseTest.php#L143 are expired?
Test failing reported at https://github.com/colemanw/webform_civicrm/pull/939#issuecomment-1906200328https://lab.civicrm.org/extensions/stripe/-/issues/465contribution fails when percentage field is enabled2024-03-21T13:05:14Zmtnpavlascontribution fails when percentage field is enabledAfter upgrading to the Civi and extension versions as listed below, contributions fail when the % field is configured and enabled in the price set.
- CiviCRM 5.69.2
- Stripe Payment Processor 6.10.2
- Payment Shared 1.2.20
- Percentage P...After upgrading to the Civi and extension versions as listed below, contributions fail when the % field is configured and enabled in the price set.
- CiviCRM 5.69.2
- Stripe Payment Processor 6.10.2
- Payment Shared 1.2.20
- Percentage Price Set Field 1.5.2
- Joomla 4.4.2
On the website (Civi contribution page) the user gets the following error message:
`Stripe An error occurred while processing the payment`
In Stripe I see the following:
```
Request parameters
{
"description": "Donate to Evergreen 8831X92675 #d973750916e515f092192009b6d48213",
"statement_descriptor_suffix": "8831X92675 D",
"statement_descriptor": "8831X92675 Donate to E",
"amount": "10350",
"customer": "cus_KbTE...."
}
Response body
{
"error": {
"code": "payment_intent_unexpected_state",
"doc_url": "https://stripe.com/docs/error-codes/payment-intent-unexpected-state",
"message": "This PaymentIntent's amount could not be updated because it has a status of requires_capture. You may only update the amount of a PaymentIntent with one of the following statuses: requires_payment_method, requires_confirmation, requires_action.",
"param": "amount",
"payment_intent": {
"id": "pi_3ObWZNLHe2ijJmBv1UzhEZ47",
"object": "payment_intent",
"amount": 10386,
"amount_capturable": 10386,
"amount_details": {
"tip": {
}
},
"amount_received": 0,
"application": null,
"application_fee_amount": null,
"automatic_payment_methods": null,
"canceled_at": null,
"cancellation_reason": null,
"capture_method": "manual",
"client_secret": "pi_3O**********************_******_*********************sk8p",
"confirmation_method": "manual",
"created": 1705964781,
"currency": "usd",
"customer": null,
"description": null,
"invoice": null,
"last_payment_error": null,
"latest_charge": "ch_3ObWZNLHe2ijJmBv17AUXXga",
"livemode": true,
"metadata": {
},
"next_action": null,
"on_behalf_of": null,
"payment_method": "pm_1ObWZLLHe2ijJmBvDkAWdhSh",
"payment_method_configuration_details": null,
"payment_method_options": {
"card": {
"installments": null,
"mandate_options": null,
"network": null,
"request_three_d_secure": "automatic"
}
},
"payment_method_types": [
"card"
],
"processing": null,
"receipt_email": null,
"review": null,
"setup_future_usage": "off_session",
"shipping": null,
"source": null,
"statement_descriptor": null,
"statement_descriptor_suffix": null,
"status": "requires_capture",
"transfer_data": null,
"transfer_group": null
},
"request_log_url": "https://dashboard.stripe.com/logs/req_H22ZX2zYJorHKW?t=1705964784",
"type": "invalid_request_error"
}
}
```
Please note the $103.86 vs. $103.50 amounts ($103.50 is the correct amount; we do not use tax in our config and price sets anywhere.)
Any thoughts on where this is coming from - Civi/% field/Stripe?
Thank you!https://lab.civicrm.org/extensions/stripe/-/issues/464Recurring payments made via stripe checkout are not properly updated2024-03-05T21:58:56ZjamieRecurring payments made via stripe checkout are not properly updatedWhen a recurring payment is created using stripe checkout, I get the following in the `civicrm_paymentprocessor_webhook` table:
```
MySQL > select id, created_date, processed_date, status,message from civicrm_paymentprocessor_webhook wh...When a recurring payment is created using stripe checkout, I get the following in the `civicrm_paymentprocessor_webhook` table:
```
MySQL > select id, created_date, processed_date, status,message from civicrm_paymentprocessor_webhook where id between 51196 and 51201 order by processed_date ;
+-------+---------------------+---------------------+---------+--------------------------------------------------------------------------------+
| id | created_date | processed_date | status | message |
+-------+---------------------+---------------------+---------+--------------------------------------------------------------------------------+
| 51197 | 2023-12-14 20:32:02 | 2023-12-14 20:32:02 | success | doCustomerSubscriptionUpdated: ignoring - not implemented |
| 51200 | 2023-12-14 20:32:03 | 2023-12-14 20:32:03 | success | doInvoicePaid: No contributionRecur record found in CiviCRM. Ignored |
| 51199 | 2023-12-14 20:32:03 | 2023-12-14 20:32:03 | success | doInvoicePaid: No contributionRecur record found in CiviCRM. Ignored |
| 51201 | 2023-12-14 20:32:03 | 2023-12-14 20:32:04 | success | doCheckoutSessionCompleted: charge.succeeded flagged for re-process. coid:1750 |
| 51196 | 2023-12-14 20:32:01 | 2023-12-14 20:45:23 | success | doChargeSucceeded: ignoring - contribution has recur |
| 51198 | 2023-12-14 20:32:02 | 2023-12-14 20:45:23 | success | doInvoiceFinalized: . coid:1750 |
+-------+---------------------+---------------------+---------+--------------------------------------------------------------------------------+
```
The `doCheckoutSessionCompleted` has a comment about how `charge.succeeded` might arrive before `checkout.session.completed` so it should be flagged for re-process. But, when it's a recurring contribution, it should be invoice.paid that should be flagged for re-process instead, because charge.succeeded ignores recurring contributions.
@mattwire I can submit a MR if you think this makes sense. Thanks!https://lab.civicrm.org/extensions/stripe/-/issues/463Drupal 10.2 webform records a console error on stripe payment2023-12-26T03:03:00ZjitendraDrupal 10.2 webform records a console error on stripe paymentCaptured in https://github.com/colemanw/webform_civicrm/actions/runs/7312817786/job/19923741300
```
There was 1 failure:
1) Drupal\Tests\webform_civicrm\FunctionalJavascript\StripeTest::testAjaxSubmitContribution
Error
at http://12...Captured in https://github.com/colemanw/webform_civicrm/actions/runs/7312817786/job/19923741300
```
There was 1 failure:
1) Drupal\Tests\webform_civicrm\FunctionalJavascript\StripeTest::testAjaxSubmitContribution
Error
at http://127.0.0.1:8080/core/misc/ajax.js?v=10.2.0:196:32
at http://127.0.0.1:8080/core/misc/ajax.js?v=10.2.0:1915:3
/home/runner/drupal/web/core/tests/Drupal/FunctionalJavascriptTests/WebDriverTestBase.php:138
/home/runner/drupal/vendor/phpunit/phpunit/src/Framework/TestResult.php:728
FAILURES!
Tests: 71, Assertions: 1878, Failures: 1, Skipped: 1.
```
Payment is done correctly, just the console error was failing the test.
Have suppressed it using https://github.com/colemanw/webform_civicrm/pull/931/files#diff-db8a63c902b85b4f8e27329f87fb00ddbe8e3c48b79241997ebb030647de45dcR81 to pass the testing, but the ajax console error is still present.
It does not happen with any other processor so seems specific to stripe? To replicate:
- Create a webform and enable ajax in webform setting.
- Enable contribution and stripe processor.
- Submit the webform with your console open.
- Notice an ajax error after submit.https://lab.civicrm.org/extensions/stripe/-/issues/462Conflict with Plans in Stripe when the membership amount and time period is t...2023-12-18T11:51:47ZRoseLaniganConflict with Plans in Stripe when the membership amount and time period is the sameWe have a number of memberships and two of them have the same value (£75 per year). When these are passed to Stripe, they use the following:
```
"plan": "every-1-year-7500-gbp", "metadata": { "Description": "Scholars' Network memb...We have a number of memberships and two of them have the same value (£75 per year). When these are passed to Stripe, they use the following:
```
"plan": "every-1-year-7500-gbp", "metadata": { "Description": "Scholars' Network membership" },
```
So the description is correct, but the Civi Stripe extension creates the plan request "every-1-year-7500-gbp" by doing this:
```
plan = "every-[frequency interval]-[frequency unit]-[amount]-[currency]"
```
The issue is that for our two memberships, this is the same thing:
"every-1-year-7500-gbp"
Stripe then uses the plan / product / price with that ID, which is the Retired plan:
https://dashboard.stripe.com/prices/every-1-year-7500-gbp
Is there a way to add another parameter so that we can distinguish between membership types in the Stripe Plans?https://lab.civicrm.org/extensions/stripe/-/issues/461Update your billing options not available on recurring receipts2023-12-07T08:35:25ZStoobUpdate your billing options not available on recurring receiptsStripe version 6.9.4, Civi 5.63.3, with Stripe configured as the default processor, we have having two possibly related issues.
1. When setting up a recurring plan the 'update your billing' details links are not available in the _email ...Stripe version 6.9.4, Civi 5.63.3, with Stripe configured as the default processor, we have having two possibly related issues.
1. When setting up a recurring plan the 'update your billing' details links are not available in the _email receipt_ (see below)
2. The email receipt is being sent inconsistently, at first it was, now it isn't at all
Is there a setting somewhere in the Stripe Extension we are missing? Is this a bug?
Or it is a feature request and not part of Stripe integration at the moment? If so, _how do_ folks update their credit card numbers or amounts on an existing plan?
Thanks!
![st](/uploads/971a271489a5fbfdeac9e35c885c949d/st.jpg)
![nos](/uploads/47e2459855d8982acfd3cbc5d9d78993/nos.jpg)https://lab.civicrm.org/extensions/stripe/-/issues/460Stripe 6.10.1 causes fatal error due to unset MOTO setting2023-11-30T17:03:27ZbrienneStripe 6.10.1 causes fatal error due to unset MOTO setting**Overview**
In Stripe 6.10.1, a fatal error is thrown when visiting a front end payment page while the user is logged in.
This error is triggered because the 'Enable Mail Order Telephone Order' setting is not set (the code expects an ar...**Overview**
In Stripe 6.10.1, a fatal error is thrown when visiting a front end payment page while the user is logged in.
This error is triggered because the 'Enable Mail Order Telephone Order' setting is not set (the code expects an array), so either the upgrade should set a value for this setting or the code should handle this value being empty.
**Replication Steps**
1. Upgrade Stripe to 6.10.1.
1. Visit a front end page where the payment widget is present (i.e. contribution page) while logged in
* Note that this does not happen if you go to the same page on a private/incognito browser, i.e. while not logged in.
1. Encounter the following TypeError
```
TypeError: in_array(): Argument #2 ($haystack) must be of type array, bool given in in_array() (line 471 of /var/www/mysite.org/web/sites/all/civicrm-custom/extensions/stripe/CRM/Core/Payment/Stripe.php)
#0 /var/www/mysite.org/web/sites/all/civicrm-custom/extensions/stripe/CRM/Core/Payment/Stripe.php(471): in_array()
#1 /var/www/mysite.org/vendor/civicrm/civicrm-core/CRM/Core/Payment/Form.php(216): CRM_Core_Payment_Stripe->buildForm()
#2 /var/www/mysite.org/vendor/civicrm/civicrm-core/CRM/Core/Payment/ProcessorForm.php(141): CRM_Core_Payment_Form::buildPaymentForm()
#3 /var/www/mysite.org/vendor/civicrm/civicrm-core/CRM/Contribute/Form/Contribution/Main.php(298): CRM_Core_Payment_ProcessorForm::buildQuickForm()
#4 /var/www/mysite.org/vendor/civicrm/civicrm-core/CRM/Core/Form.php(730): CRM_Contribute_Form_Contribution_Main->buildQuickForm()
#5 /var/www/mysite.org/vendor/civicrm/civicrm-core/CRM/Core/QuickForm/Action/Display.php(76): CRM_Core_Form->buildForm()
#6 /var/www/mysite.org/vendor/civicrm/civicrm-packages/HTML/QuickForm/Controller.php(203): CRM_Core_QuickForm_Action_Display->perform()
#7 /var/www/mysite.org/vendor/civicrm/civicrm-packages/HTML/QuickForm/Page.php(103): HTML_QuickForm_Controller->handle()
#8 /var/www/mysite.org/vendor/civicrm/civicrm-core/CRM/Core/Controller.php(355): HTML_QuickForm_Page->handle()
#9 /var/www/mysite.org/vendor/civicrm/civicrm-core/CRM/Core/Invoke.php(322): CRM_Core_Controller->run()
#10 /var/www/mysite.org/vendor/civicrm/civicrm-core/CRM/Core/Invoke.php(69): CRM_Core_Invoke::runItem()
#11 /var/www/mysite.org/vendor/civicrm/civicrm-core/CRM/Core/Invoke.php(36): CRM_Core_Invoke::_invoke()
#12 /var/www/mysite.org/web/modules/contrib/civicrm/src/Civicrm.php(88): CRM_Core_Invoke::invoke()
#13 /var/www/mysite.org/web/modules/contrib/civicrm/src/Controller/CivicrmController.php(83): Drupal\civicrm\Civicrm->invoke()
#14 [internal function]: Drupal\civicrm\Controller\CivicrmController->main()
#15 /var/www/mysite.org/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(123): call_user_func_array()
#16 /var/www/mysite.org/web/core/lib/Drupal/Core/Render/Renderer.php(580): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}()
#17 /var/www/mysite.org/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(124): Drupal\Core\Render\Renderer->executeInRenderContext()
#18 /var/www/mysite.org/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(97): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext()
#19 /var/www/mysite.org/vendor/symfony/http-kernel/HttpKernel.php(169): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}()
#20 /var/www/mysite.org/vendor/symfony/http-kernel/HttpKernel.php(81): Symfony\Component\HttpKernel\HttpKernel->handleRaw()
#21 /var/www/mysite.org/web/core/lib/Drupal/Core/StackMiddleware/Session.php(58): Symfony\Component\HttpKernel\HttpKernel->handle()
#22 /var/www/mysite.org/web/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(48): Drupal\Core\StackMiddleware\Session->handle()
#23 /var/www/mysite.org/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(106): Drupal\Core\StackMiddleware\KernelPreHandle->handle()
#24 /var/www/mysite.org/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(85): Drupal\page_cache\StackMiddleware\PageCache->pass()
#25 /var/www/mysite.org/web/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(48): Drupal\page_cache\StackMiddleware\PageCache->handle()
#26 /var/www/mysite.org/web/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(51): Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle()
#27 /var/www/mysite.org/vendor/stack/builder/src/Stack/StackedHttpKernel.php(23): Drupal\Core\StackMiddleware\NegotiationMiddleware->handle()
#28 /var/www/mysite.org/web/core/lib/Drupal/Core/DrupalKernel.php(718): Stack\StackedHttpKernel->handle()
#29 /var/www/mysite.org/web/index.php(19): Drupal\Core\DrupalKernel->handle()
#30 {main}
```6.10https://lab.civicrm.org/extensions/stripe/-/issues/459Auto-Fill Credit Card Resets Number of Participants2023-11-14T17:14:00ZBdanielsAuto-Fill Credit Card Resets Number of ParticipantsIf you have an event that allows multiple participants and is using Stripe, the number of participants value is reset to "1" if you auto-fill your credit card information. Issue verified in Chrome but haven't tested other browsers.
- In...If you have an event that allows multiple participants and is using Stripe, the number of participants value is reset to "1" if you auto-fill your credit card information. Issue verified in Chrome but haven't tested other browsers.
- In Chrome, enter this in the URL chrome://settings/payments
- Enable "Save and fill payment methods"
- Then an "Add" button should appear
- In the popup, enter the dummy credit card info.
- Go to an event registration form
- Select more than one participant
- Click into the credit card field and select the dummy credit card to auto-fill the information
- The Number of Participants field value is reset to "1"
See recording below and watch the value in the number of participants field. You will see that the value in the field changes as soon as I hover over the auto-fill option. Then when I select the credit card to auto-fill the details, the number of participants value sticks.
![Event-Participant-auto-fill-credit-card-issue](/uploads/c51c873188517291ae4864dfa3f9cd2d/Event-Participant-auto-fill-credit-card-issue.mp4)
Issue confirmed in Chrome Version 119.0.6045.123 (Official Build) (x86_64) but may be occurring in other browsers according to a client report.
I'm able to recreate in a site running:
* Drupal 7.97
* CiviCRM 5.63.4
* Stripe extension 6.9.1
As well as a site running:
* Drupal 9.5.11
* CiviCRM 5.51.4
* Stripe extension 6.7.14https://lab.civicrm.org/extensions/stripe/-/issues/458Remove 'Save with Link' button2023-11-29T20:40:27ZBruce ThompsonRemove 'Save with Link' buttonWe are trying to remove the 'Save with Link' button from the Stripe entry area. It shows after all the card info is submitted and if clicked it generates a pop-up asking the user to login or create an account to save their payment info f...We are trying to remove the 'Save with Link' button from the Stripe entry area. It shows after all the card info is submitted and if clicked it generates a pop-up asking the user to login or create an account to save their payment info for further use. It is causing some confusion for users and we want to just not offer the option. We went into the Stripe Dashboard and disabled the 'Link' option for checkout but the button still shows. Is there something else we need to do?
CiviCRM v5.64.4, Stripe Extension v6.10, Payment Shared Extension v1.2.17
WordPress CMS
Thanks6.10https://lab.civicrm.org/extensions/stripe/-/issues/457Payment Processor ID change and webhook2023-11-06T17:39:13ZbrianpPayment Processor ID change and webhookRecurring payments are processing correctly on Stripe and showing as successfully posting back to CiviCRM, but the webhook is returning this error:
Event (evt_1O89ZeAa1SNaJ0Pdoly6Dt8n) is not for this payment processor - ignoring. CiviC...Recurring payments are processing correctly on Stripe and showing as successfully posting back to CiviCRM, but the webhook is returning this error:
Event (evt_1O89ZeAa1SNaJ0Pdoly6Dt8n) is not for this payment processor - ignoring. CiviCRM: Stripe_Checkout (Live).
We changed the payment processor for the site after the subscription was created. I can't seem to find what table needs to get updated so the payment processor ID and recurring subscription match and the CiviCRM transacations actually get updated.
Any ideas?
Thankshttps://lab.civicrm.org/extensions/stripe/-/issues/456no email event registration confirmation when paying via Stripe Checkout2024-02-09T14:19:06Zjamieno email event registration confirmation when paying via Stripe CheckoutI saw this in [mattermost back in September](https://chat.civicrm.org/civicrm/pl/gw55777ak7gmbeizsyjeqk8ehr) and also have this problem.
With a paid event that includes a email receipt option, configured to use Stripe Checkout, no email...I saw this in [mattermost back in September](https://chat.civicrm.org/civicrm/pl/gw55777ak7gmbeizsyjeqk8ehr) and also have this problem.
With a paid event that includes a email receipt option, configured to use Stripe Checkout, no email confirmation message is sent upon a successful checkout.
When a $0 option is selected, the user is not redirected to Stripe Checkout, and an email is sent. But when a registration option is selected that includes an amount, we are directed to Stripe Checkout and everything works properly *except* no email confirmation is set.
I'm going to be digging in to try to figure it out - but if anyone sees this and has clues as to where to start, they would be appreciated.https://lab.civicrm.org/extensions/stripe/-/issues/455400 Errors on Stripe2023-10-19T15:26:18Zbrianp400 Errors on StripeWe recently upgraded to 6.10 and enabled the stripe checkout. Transactions are being posted to Stripe and are succcessful, but the post back to CiviCRM is returning a 400 error. The receipt page shows on the CiviCRM site, but it has the ...We recently upgraded to 6.10 and enabled the stripe checkout. Transactions are being posted to Stripe and are succcessful, but the post back to CiviCRM is returning a 400 error. The receipt page shows on the CiviCRM site, but it has the message that the charge has been submitted for processing and a receipt will be sent later. When we look at the contribution record for the user it shows as pending and an incomplete transacation. I deleted the webhooks and let the extension create them again, but that did not seem to fix it,https://lab.civicrm.org/extensions/stripe/-/issues/454Multiple participant paid event registration workflow2024-02-25T09:53:47ZUpperholmeMultiple participant paid event registration workflowA while back in #387 I think I wrote:
"I'm using 6.7.10 (with Civi 5.53 and WP 6.02) and multi-participant event registration isn't working, which has brought me here. If I select more than one participant the stripe box appears straigh...A while back in #387 I think I wrote:
"I'm using 6.7.10 (with Civi 5.53 and WP 6.02) and multi-participant event registration isn't working, which has brought me here. If I select more than one participant the stripe box appears straight away on the form (with only one participant it doesn't show until a price option is selected), and then appears to pre-authorise before I even get to the second participant.
I need to explore what's happening in more detail, but I've had two people try and fail to register two participants in the last couple of days. The test drive seemed to work, so maybe it's just the weird workflow that is confusing users. It simply doesn't make sense to get the user to input card details until they have entered all of the participant information."
As far as I can see it is still the case (I'm currently using v 6.9.4 of this extension) that when choosing to register more than 1 participant, the stripe card details box appears at the bottom of the first page of the form regardless as to whether the user has selected to pay using Stripe (in my use case they can choose the Stripe card payment option or to pay later). This in itself is weird, but asking for card details on the first page really doesn't make any sense form a user experience perspective, and is causing confusion with users.
What should happen with a multi-participant paid event?
In my view the user should be able to input all of the details and options for all of their participants, and then go to a confirmation screen which lists all of that out and gives them a total cost and the option to go back and change things. Assuming they are content with their input they should then go to a payment page where they choose their payment preference if given the choice, and provide the card details for Stripe, do the 3D-secure verification as appropriate, and then get their receipt and invoice etc.
I can't think of any other online payment process where I am asked to provide card details before I even know how much its going to cost me.
I'm sure there was a point in this extension's life where there was a config option about this workflow, but now I can't find anything about it. If I've missed that please forgive me and point me in the right direction.