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
- b46f81d25c2b2767b0333e0fc872f4e3ec6946984e5b9f841a950423b4903193
- request
- c84b6c1494d76747f9b02382d206edb9ae76d68736bb19d489a6d485a80fe34d
- transaction
- 02d54764ecebad9eca01d26bdcd305cf058722e67f8735a53137d0218c85aae3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14229
the chainentry 14229
- sealed to the entry before
- 3b545b49e1897f4eccf38487f9e911e4a63644d09b303ee551a515b0c840d247
- this leaf
- b25714bc76e866690223c126211efb779269c5056ba51a4f7defdd1dde13f5e1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ejoXH2svmcQsXVkKX3cStlniGK2pgXI2RD947I2dtyx3cbDt0Z8KkDb/0j1Pz8CAwPiv3mCD96dNAtME5tKVCw==