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
- 3a2cc1dc33b2ce10f2d80422d65abbd09c8112ce424fbadab5c6ad2a40ecbbe1
- request
- 27769bd228726046927902ed81df5317212c12468968a803220539a88d6ac085
- transaction
- 3a40777a6180a9167997c7337a331a8c493f55101fab64921876fcebc4b943c4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23535
the chainentry 23535
- sealed to the entry before
- dd44d94adb1a8e958526deed40a94daaa6e507db11dd07e57ae1e076c5532419
- this leaf
- dba4bf010ce2c41411424e4e2b89a3889fb55862157fdbfae68cdf7ab2c76813
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hS9PBJ3p7Oigq1zGPDAc0MWxTRDG4yO92rNSIW7hLUHpyYxT7x/0MhFKTZVqvqu9AkGEAEF/qhGQhwSna7MGCw==