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
- 9ff57494240a6d8765ed4f8db2fb5d5c3124d5d7f3bbabab7f848f21acf9eb84
- request
- 48b4c38a1f408233f86f7e7c4bd7c00419e08144af196311bda88baac92cd3ed
- transaction
- b6860492924b0aa0f2f13ddf0da673070bf279c8f1304d43767d7e5fe2ef1a21computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51735
the chainentry 51735
- sealed to the entry before
- d4f329f0a11718e10f0aea7a2ad3e7c1bc0acaaa58d242f3ab45088fd82431b7
- this leaf
- 8a0279b2d3676335cc7987d65e5c5b6326b5a6a4631774da303bbe15b38db263
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eibcXSWvbOM3vLWzF/tfL7SFMbE1INWn6uAMrHduVbgDl6XY8AjYVO3NfWoROUMrzlg1uGJx6+0YOKH98YQkBg==