|
|
Assigning this to you, @stefan, if I may: first, you should check if the more fundamental problem is really solved, as soon as the taler-merchant could be upgraded. |
|
|
We will test the template functionality with the 4 to 6 instances in the Merchant Backoffice with real Swiss Francs, hereby also testing settlement which was not on the test agenda so much before. |
|
|
Good match: I wanted to add a ticket on settlement tests, already. Will do next. |
|
|
In the morning, I had v1.2.1, after update on the self-hosted subdomain we had Merchant Backoffice 1.1.1 again which is clearly a downgrade. So, waiting for v1.2.3 makes sense, but first backup procedures need to be run on the server. See the pic attached. Merchant_upgrade_leads_to_downgrade_of_version.png (177,150 bytes) |
|
|
- Settlement from SK's instance hacktivismch4sp for order no. 2025.323-01841DV44YG5P (which was paid on Nov 19) was NOT transferred to HM's bank account with an amount of CHF 0.1 - We checked HM's bank account slip on Tuesday, Dec 2nd, 11 days after the wire deadline configured in the Merchant Backend. - The BCF bank account was successfully KYC'ed, all seemed fine with this instance and its linked bank account. |
|
|
@stefan: JFYI, a specific settlements ticket exists with 0010689, not sure if settlement-specifics can make sense here; I understood, it shall be possible to define delays specifically to specific order types by using templates. Then this might make sense here. On the other hand, more generic, not template-specific tests, are possible; most orders I created, for sure all the ones in the beginning, were created with simple orders which could be claimed only once, not using the templates system. => I will add at least all those cases over there to 0010689. |
- Anonymous
