why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- f659bbe6805274162de43eff92db8ab6d2d1ce0833f03200de1945b762c3fae5
- request
- d79897334d058f821eaccfcebec2580fa1362df5b8b358d5a0ac5a0adea34ab3
- transaction
- 9b18d25503018f08a828a72ac7a19a99a102ef9248304d7f0a04623cdfcfccd9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49408
the chainentry 49408
- sealed to the entry before
- 47fa3b4959264086620ea98cbf18b4e0644cf56c3cdb95fba750ef62774f3c03
- this leaf
- bb4956f1efcdd2108eb9e0c7874e2ef5f3c9152d35fa6cf03502feed5184beb8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uERwVdA6PU+DVTUJ9o+gZQhVqV9fAZDo4BBnv2BpteNgRSxNNzpuZWO8h2mo8r8mQYIOZEI8c8w4xTfGYHmlBQ==