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
- 11f83ab296d255fec633b8145ff502acac479801f2f0b64e9627e772380a5700
- request
- 3c10c47b9ca8ccf43a73017255c2332260bd1987619f3d71a76ce6720eda7a7c
- transaction
- d7311843f6f752b6cd6b5956bbe1a3ebbef7a58824dd9322a3f44cfd78fbe58acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1680
the chainentry 1680
- sealed to the entry before
- 0c1df7ca548b27f50fe441311e98ebac10e7b9d167fc708214c28f72fb9884dc
- this leaf
- 38f090258f07350320096aabc1acb8a7ac9ead8900bef9da07537a69128d78d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- P7Oqh6PpT5wuj3bwBscmPFQPgaTL0iaKhH4EXfpYcSmoxEs/WbK5WWqThtF4qW7EVH3Yl9IIcce80QwDnVtKDQ==