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
- baf09bfa6f4e47ee9c9b1bf075d5bc70e08f68f4b69b995a290934fe51f8772b
- request
- 43173aeac31fb267d85f1ad2dee526a4527833d35c004955733347b2c80cfbd3
- transaction
- 1d1739ae0fe43ec1d0638458674928e6fae2355429b2a33ffcd5eca61e99c92fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7955
the chainentry 7955
- sealed to the entry before
- 290bab18887ab760a26148120cd36134e95a35898a8045240a17a39843862c9f
- this leaf
- 8350a151de6ead462f74dcd3386b723930eee541862047ca9282f48fe7346e7a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iaQnjB1acoCaInvy866vaYZiv7wvy5QW+POxOEiCXZ10Z2E6fept31D6PzCase01x3+xwlFilTtKiWJhN8FVCQ==