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
- a30119343a8f9ae11dd65b20b514fc590debe2d948861c62bc57ff7efffd62b6
- request
- b08a44f09f1e80f12255ff54d6a1ff91a736cc704b807dd569f89d853ccfaed0
- transaction
- db3f7ad6be733f4ceab4d303960026f8ea919c9c9bc15db10d16ae8e66352d2ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42914
the chainentry 42914
- sealed to the entry before
- 4aae15c339ea4f477d4b27ce7187ff41897c2a3d7493250bfa64e858579ca35e
- this leaf
- fc4f33dbbac02597543a01c4b58709662670e966180ec4e87955a1e9e1e4bd18
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2LGAdbQ5cn4u2/r6wkgKtPyZ+r4VBrm6HwyFNO8+KEk4O+FDFQh5DFOc4jVV43QN9n4+j9bcrY5RUqINq/3SAA==