• Resolved nickfarelli

    (@nickfarelli)


    Hi there,

    the following problem existis for at least 6 months, i didn’t report it yet because i always thought it not appear anymore at some time ??

    So: The data of the orders is passed wrong to the stripe dashboard.
    When looking up the transaction reports, you can see the problem: The payment ID often is not in the right column. Often it’s in the column of the NAME of the person who pays.

    The problem is visible directly after the payment and as i can see only affects orders which are paid with SOFORT.

    When you look up the order of the affected payments, you cannot click the transaction ID anymore. There is no link. Exactly these order where the link of the transaction ID can’t be clicked are later the orders which are not displayed correctly in the transaction report.

    So there must be a problem how woocommerce processes payment data.

    This leads to several problems:

    1. All transaction reports from stripe have wrong column that have to be fixed manually, which takes about 6 hours monthly.
    2. This is necessary since the transaction reports have to be passed correctly to our tax consultant. Because the columns are shifted, for example every order which is affected gets the invoice number of another order which is above that.

    I can send you transaction reports as well give you access to our wp dashbboard if you want.

    Here is a picture that shows the problem:

    View post on imgur.com

    • This topic was modified 4 years, 12 months ago by nickfarelli.
Viewing 2 replies - 1 through 2 (of 2 total)
  • When you look up the order of the affected payments, you cannot click the transaction ID anymore. There is no link

    Presumably, you are talking about this:

    If I’ve got that right, then that is an indication that there is a fatal error happening. If there are fatal errors happening, then I would expect you could find evidence of that in the WooCommerce logs. WooCommerce -> Status -> Logs and then in the dropdown selector, look for any logs where the name begins with fatal-errors, followed by a date/time, followed by random letters/numbers.

    If there are any fatal errors, take the necessary steps to get those resolved.

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘payment data passed wrong – buggy transaction reports [SOFORT]’ is closed to new replies.