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
- da3ab8c4e2eecc237a252f1fe3a48f8bd02e34dc28e11c7361000729ff5ce5c1
- request
- 765555d11427a730eec42f36d935ccd6dc6cd4f133113c044e171221f1bac65e
- transaction
- d384fc7243b20fe78d35e94f13785af1556adb7fa83004f2d60c7193b558de94computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15494
the chainentry 15494
- sealed to the entry before
- 822319a3a841c1bbfcc2d9641f07f16834b43fa348f917d063a71af5dd450441
- this leaf
- 40affbef35a77ee6e47a67dcf5dd6f33ea17f61d88e1456c752429fe026f2edd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HDr+bbYvhQBpPjZu+zAqZcyYDnyRKmIOgC8mKZf19DUKvH/FCDlYquk+u0JMvBes8uPxDni/1k24+ofrR8k4Dw==