search

Project60 / org.project60.sepapp

CiviCRM PaymentProcessor for CiviSEPA
Other
4 stars 4 forks source link

SEPA payment processor (classic version) produces extra (erroneous) financial_transactions #18

Open Detsieber opened 1 year ago

Detsieber commented 1 year ago

Actual behaviour: The classical SEPA payment processor creates a (wrong) financial_transaction record in the table civicrm_financial_trxn, at the time the mandate is entered. These entries are marked as "completed", and have a wrong payment method.

When the SEPA group is marked as "received", another financial_transaction record is created, with the correct values.

This creates severe problems for use cases, that are using the table civicrm_financial_trxn: e.g. CiviCRM invoices, accounting export.

The issue is only happening with OOFF payments, not with FRST/RCUR payments.

Workaround:

With the SEPA NG payment processor, this does not happen. However, the SEPA NG payment processor currently does not support event payments (see #17)

UeNu9 commented 1 year ago

We are experiencing the same problem in our system, using Memberships that create One-off Contributions: https://civicrm.stackexchange.com/questions/44791/creation-of-one-off-membership-creates-a-completed-payment-too