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
- c795b32cc84ca1bc01e5a3303ab8ea44bd1f62b75817187b1e718c42f276e643
- request
- d781ae9d679ba04a0d90f980bf863e06d541004bfd18b5871ff755db34fa8e86
- transaction
- d81dc913c52baf95d060a27c4f784d15143432cfc50419b0d1c594511f4012decomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71679
the chainentry 71679
- sealed to the entry before
- 15f6c9a360889314364ba6c68ef466cc989def782123889e0ce5fce733f0842f
- this leaf
- 058124b2a7b1af8b4be1958cbf4058ad35b54d28fd4d79912eb476ed3a59faad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B5R2cRif4dBpCP2ccp8tG2eNR66/+A3fnL9Hglb1aiG7esCnUUzbIjhkdSBcYGT7NhOWDvhtJRXYhloDeHxqDw==