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
- b8ac2fe6298cee1dc5498f3ea25b1292a232a5e64fa4dc5d5b37ddb8f199efb7
- request
- d1b679684edc676598508153a400dc335495868d89a6255011e5b1ab1039e1c6
- transaction
- 1907066ab1999f02a7efc3e825d12ec33433e3dc1134f61ffc9a23e8866fcd92computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67284
the chainentry 67284
- sealed to the entry before
- 85968f1453b666427e52878f14facb84c094491d0e03e44c6a5bc838a01886e5
- this leaf
- dc1d1e5a6235e1583968cd967f23c1189d0b98c6d7cd050d3e608926b52b2868
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GA7I8TAFP4jQsL9i+8+666u3MhRkyoWl/1z7cOwIfCGub7f7TeAAkgPYI6Mu0CmkA6nS4lIg+oTbpMTLoAI2Cg==