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
- 4a4329ae75cd99171c57fa281d5570a79c7c330705166081d2233a07b2f60d55
- request
- 679cc00be1ad523a4eeb85491368ae453695b0fa24dd3594a3f5646702860354
- transaction
- 144ab7451e72ce9974bddcd1b74cd936d1e16b4ccd8e1834bd0758fa6acc7669computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46919
the chainentry 46919
- sealed to the entry before
- e52772774f805de9dc6be71cc0ccaa3086d8012ed4bfffed71bb54b293479c0b
- this leaf
- 681d8589208b1c34952c93ac5e88162ab7ff9fd3ce0938d6713e1985003f24f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cFaBh9B5f+7mqDjL7IcffXPRm4t52xaSJBeZHffK+2Yq+bKc1MLndEb1XKg5KnbE3AG0/oiB6RPNC3l++2f2DA==