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
- ada11677703ba0a729e84a2e05fe2cd6f1dd889367005b4ebee5f31b8f8a0247
- request
- efbf351dfc4c83fe7fef5bb60b95d4523ffad3c8eb7e470ce2f2773f1899f2a1
- transaction
- c60e815b667c4165109ca592ee3e7c7a3e3289238d4f6c94f433a5257016f95fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65603
the chainentry 65603
- sealed to the entry before
- 513ff369b44d30301a86ec2d666ebedb1736f83092e6802fb2c3f1c5c5fd83fe
- this leaf
- 26d1ad7a1207bbeef2100e638d545db668560ec882de13a33a3835ac57ae0715
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ukYDtGBT8qnzE1prhq/I0FGo3CoExHHIUqC+aqKgAWU1fPx9lb3XS1zbouMc9xRPzYMrT7/9BOk9eSuIVk2NAw==