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
- 42396b1a05f867675be212195fd742532eaae4ded80a58894448e54a9fc42b30
- request
- 0c3723064bc0b26c0250422d74ae1231295eb4bfc8f5c103cc9e79af5ece5056
- transaction
- 47a988a098e2fda5bde094fcee67b2a3e5a76738a48c3ec9870324be089c0425computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68770
the chainentry 68770
- sealed to the entry before
- e444cc5ce96f9ab1767e49a73b735ee9d9dda4bea9144d2fbd1689628a15b110
- this leaf
- 254131c1d7e4604bbe0c9bfc7a7660f3beb23d753ca77732600d98ad365936fd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ggfEXVxhg1PAv/ZTlFXxDrBTgbfUig74DBo3y6aMUs2bYGcg1fugB0ICmOoZhunBwEnO8vkdr01TnQ6k4+TOBA==