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
- 3ab9fa30884d1cecc3c8658533eaa2d48a0f7fa389cfc1def9cd91e0e4234d54
- request
- 7b6457d7da1510cbab9c5f712d6200b55b4f8f52a1a060d0e55c70608ce198ed
- transaction
- ce5d0d73bca21a880dccedef8975335f57dda31addfc0b01f454f94738ecc3a1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35600
the chainentry 35600
- sealed to the entry before
- 1790262d39eedf6de5923dbe8868f7499b9fead663b725d1a8414db9fcdb1b2e
- this leaf
- c375a68310daaa4d7f2636547d969849560102550248d28de261cd4973a91769
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fhCHDh25EmUKOTosUtFgYC/jt91N4TC++Z9gEEV8Y7eeXpmFtrWV/zjZonYSELgYaGMzshTW4lQyk9tBkL3dAg==