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
- a3b7e926e1ae6e2539a829ef1e553bcc8693a08f566967c9e83e3d69569462e0
- request
- 52b98514eef08511ec93d68fd5a5fac028429524ca8ad5317c600bffa8192b2b
- transaction
- 1c1df724a74124ce8b81c97453dc8a04e64e57f44ebd2548335d3e7fdc55b78acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44509
the chainentry 44509
- sealed to the entry before
- c376ecdde6656a4c0f24b9c653d71915062314da80e432d4dd9940b5f3595e60
- this leaf
- 2dfe31b7dbfa8f15f898be6754ec9862f88be59046f98c8b0fd4621e02ffd757
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8/L81x61eWAJYZmgm5p6ruCvVS3GzNwgyATZwCNWb8c1SsMI9vgUgvspt1IWSfzFbiObRqymWiDE8swQcwaqAw==