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
- 38b1e23972ed97d8eff908853f9c9ea3954ae3d36cb5fbced69c8a06748963ca
- request
- 25ffd63262901642eada5804ba758d09aa4240ca92ed908c5173a138194a35dd
- transaction
- c396460d4838089988b9101aae27133918fe659a4e4650de8fc1cd975f5d65e7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10851
the chainentry 10851
- sealed to the entry before
- 88711f0dd731c0497b934baf55d5397c7928dabe089550aab9ac2116845cb1fc
- this leaf
- 4873b6498cc7580e1e4c1696a7ebb140093e4c2c2e3d1561df429374e02b98d9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KytgPVZSXVzByrbrqgqLCRNP/nZAw7mT4PMMu9lDI9Imqq7A7fXFSZoQVBua8bDwgd9EOw46Kb5vOHdFPWcdCA==