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
- e309ca7501487b477e71a02ffb5e3bcebb9bf3b369db37d0d0c1d1f49a900542
- request
- e02580e596768a7b6920bc215f31f57ec245b34f73c9d5df298b292a42f7da77
- transaction
- c0e2808d84b39c835dec4a28eac7032c8627e60ccb400e4804d124df29e2582ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76454
the chainentry 76454
- sealed to the entry before
- 959638222febb23e23e63309caa3ea3c611d278e15abf595ae864d98e35972d2
- this leaf
- 8eb98821783ac218d42ab555a8cc7c620c1a6decf9a14ca8bab642ccb54c90f8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qF6WiVc9W5HWwM4eSdGd8uydxdmbGMpLb1SBloVHR/oLGFzs/8PkNaVe6gOIvHrhW4v9ouQ2a2igdf95EaKlAg==