Stripe issueshttps://lab.civicrm.org/extensions/stripe/-/issues2024-03-28T21:26:04Zhttps://lab.civicrm.org/extensions/stripe/-/issues/474What does the Stripe security requirements 'change' mean2024-03-28T21:26:04ZeileenWhat does the Stripe security requirements 'change' mean
Josh got this email from Stripe - what does it mean for us?
=================================================================================
Thanks again for taking the time to meet with us and discuss the CiviCRM plugin and ways tha...
Josh got this email from Stripe - what does it mean for us?
=================================================================================
Thanks again for taking the time to meet with us and discuss the CiviCRM plugin and ways that we can deepen our partnership. As we mentioned on the call, Stripe is heightening our security standards by requiring all plugin developers and merchants to use a Stripe Apps supported authentication method.
There are 2 ways CiviCRM can achieve these new security requirements: by implementing either OAuth or Restricted API key (RAK) authentication via a Stripe App, and/or migrating to standard Connect. Please review the [technical onboarding guide](https://stripe.com/docs/stripe-apps/onboarding-plugin) and documentation for [OAuth](https://stripe.com/docs/stripe-apps/api-authentication/oauth) Apps and [RAK](https://stripe.com/docs/stripe-apps/api-authentication/rak) Apps.
All plugin developers using unrestricted API keys must complete the security upgrade by June 2024 in order to avoid any impact to your plugin. Below is a high level timeline of this deprecation:
* April ‘24 - Stripe will send a security risk notification to all merchants using non-secure plugins and will add a security flag on all non-secure plugins in the Stripe Dashboard.
* August ‘24 - Stripe will begin to deprecate the use of non-secure plugins.
Upgrading to Stripe Apps will not only help you meet these security requirements, but can also help you increase your plugin’s distribution. As part of the update, we are offering all developers a Stripe App Marketplace listing, plugin analytics dashboards, and an invitation to [Stripe’s Partner Program](https://docs.stripe.com/partners#benefits).
In addition, the Stripe Apps marketplace and our new, more secure framework do not support legacy integrations. *As such, we will require all plugins in the Stripe Apps marketplace to be on non-legacy UIs (Card Element) in order to ensure the best user and merchant experience.* By implementing Stripe's Optimized Checkout Suite ([payment elements](https://stripe.com/docs/payments/payment-element/migration), [payment methods](https://stripe.com/docs/payments/elements/link-authentication-element), and [Link](https://stripe.com/docs/payments/elements/link-authentication-element)) CiviCRM can leverage our newest checkout products and drive revenue.
Please let us know once you've had a chance to review with your team. We would like to schedule a follow up call later this week or next to help you scope your upgrades, discuss Connect revshare opportunity, and answer any technical questions.https://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/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-29T12:40:04Zmtnpavlascontribution 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/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/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/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/452Delay up to few hours or NO receipt for completed payment2023-09-26T03:44:09ZtapashDelay up to few hours or NO receipt for completed paymentCivi - 5.65.2, Latest-stripe checkout
There seems to be a random delay in sending receipts for completed payment. Sometimes it gets sent in 10 min, sometimes it takes couple of hours. I have cron job running every 10 min. For events sig...Civi - 5.65.2, Latest-stripe checkout
There seems to be a random delay in sending receipts for completed payment. Sometimes it gets sent in 10 min, sometimes it takes couple of hours. I have cron job running every 10 min. For events signup, receipts are not even sent, although I see stripe marks the log as receipt sent.
It confuses people because they think payment is not completed and make an attempt to pay again. I have had a numerous complains about it. Is this something you are aware of @mattwire ? Thankshttps://lab.civicrm.org/extensions/stripe/-/issues/451Cannot process a amount with a decimal value like £1.132023-09-25T16:38:43ZtapashCannot process a amount with a decimal value like £1.13It only works nearest to the £. The fraction payment comes with an error. Tested with stripe checkout. @mattwire
_`Stripe(8): doPayment: Stripe\Exception\InvalidRequestException: Invalid integer: 1.13`_It only works nearest to the £. The fraction payment comes with an error. Tested with stripe checkout. @mattwire
_`Stripe(8): doPayment: Stripe\Exception\InvalidRequestException: Invalid integer: 1.13`_https://lab.civicrm.org/extensions/stripe/-/issues/450jQuery Validation placement different from CiviCRM2023-09-14T15:24:27ZJonny ToomeyjQuery Validation placement different from CiviCRMHi there
When using the Stripe extension on a Event Registration form the placement of error messages for checkboxes is different to when we other payment processors. I've spent some time trying to override the errorPlacement option but...Hi there
When using the Stripe extension on a Event Registration form the placement of error messages for checkboxes is different to when we other payment processors. I've spent some time trying to override the errorPlacement option but cannot find a way
Would it be possible to make the default placement match the Civi default jquery validation or advise on how I can override it for Stripe?
Best wishes
Jonny
# not stripe
![not_stripe](/uploads/07cb752bb32baedf2d6a5380f3e4e53b/not_stripe.PNG)
# stripe
![stripe](/uploads/e8c656a93c1bdc376f011409c4ae3763/stripe.PNG)https://lab.civicrm.org/extensions/stripe/-/issues/445CiviEvent Registration Completes, but related Stripe payment is "Incomplete"2023-11-07T10:17:31ZmarcusjwilsonCiviEvent Registration Completes, but related Stripe payment is "Incomplete"@mattwire I think this might be the same as this issue: https://lab.civicrm.org/extensions/stripe/-/issues/435
We're seeing a worrying issue on Civi 5.63.3/Stripe 6.9.2/Payment Shared 1.2.14 where the Stripe payment form has been moved ...@mattwire I think this might be the same as this issue: https://lab.civicrm.org/extensions/stripe/-/issues/435
We're seeing a worrying issue on Civi 5.63.3/Stripe 6.9.2/Payment Shared 1.2.14 where the Stripe payment form has been moved to the Confirmation screen.
Consistently, paid Stripe registrations are being reported as "Completed" in CiviEvent, when they are "Incomplete" in Stripe.
Not sure if this is an edge case, but I'm not sure why there should ever be a situation where payment is Incomplete in Stripe but marked as Completed in Civi?
Best wishes
Marcushttps://lab.civicrm.org/extensions/stripe/-/issues/444Localization confuses the webhook missing status checker2023-08-06T13:38:45ZjamieLocalization confuses the webhook missing status checkerWhen installed via a Drupal CRM with localization (that uses the URL, e.g. crm.example.org/es/civicrm/), the status check that ensures all webhooks are properly installed gives a false alert about a missing webhook (crm.example.org/es/ci...When installed via a Drupal CRM with localization (that uses the URL, e.g. crm.example.org/es/civicrm/), the status check that ensures all webhooks are properly installed gives a false alert about a missing webhook (crm.example.org/es/civicrm/payment/ipn/1). It should detect that crm.example.org/civicrm/payment/ipn/1 is properly installed and not give this warning.jamiejamiehttps://lab.civicrm.org/extensions/stripe/-/issues/442Duplicate contribution created for recurring payments in Stripe v6.9.12024-03-14T15:39:16ZwmortadaDuplicate contribution created for recurring payments in Stripe v6.9.1If a user makes a recurring payment with Stripe two contributions are created. The first contribution has status Completed and is as expected. But there is a second contribution that has status Pending for the same amount and at the same...If a user makes a recurring payment with Stripe two contributions are created. The first contribution has status Completed and is as expected. But there is a second contribution that has status Pending for the same amount and at the same time. The ID of the pending contribution is higher so was presumably created later.
We have come across this issue on three separate sites running different versions of CiviCRM (5.62.1 and 5.63.1).
Our testing indicates that this is an issue for both existing contacts and new contacts. It affects both logged in and logged out users. It's an issue for both monthly and annual payments. I've tested with and without a confirmation page.
~~Both sites were previously on the Stripe extension 6.8.2 and this issue wasn't present.~~
Environment:
* Stripe extension versions: 6.7.14, 6.9.1 and 6.9.3
* CiviCRM versions: 5.62.1, 5.63.1 and 5.64.4
* Drupal 7.98 / WordPress 6.2.2
* PHP 8.1 (also tested in PHP 8.0 and 7.4)
One site is in production the other two are test sites with the contribution pages in test drive mode.