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
- fdd226f41225f4f58829da2f4590e7ca9eff19effaf8f7787f61e7797ec3c3fa
- request
- cff549222e521ce92c75a5db8a012292b7b754059b23c0983ce91bd041c659d4
- transaction
- dc71f5e47916c1e80582aec3f51813265509b68110b09dbfff73350ce0469749computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16151
the chainentry 16151
- sealed to the entry before
- d9017b8fd2f6df7cafad4a8e57e99b2a00e76c5dc61c34df4382bfba14c41d98
- this leaf
- 2074cb0d0030a76c9f5a4c795bc4f1ce5c12379cc3f9534ae10b5490e064d0a2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZYxnMhQWb8ArGZ+m4rMYBweY6Q21pBm933UZWGPTtCOw5+TxFHoVE2n7yv4+HvgtAgB2SGfsdX7MPsYhplqSCg==