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
- c0ccab6a1bffab91387fa25b69703a0c6b4e62bbea4b509af53014c5906d8662
- request
- 9dc87f5312abfe3076edc3844b07eedc23ec8a2d30ec90afa07bdbdfa67192d9
- transaction
- 522fe2c6f4a4e558290cd9e9f91efd67569b376ac71a578a051d6168e1f02745computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33777
the chainentry 33777
- sealed to the entry before
- cc5313c2cc4937c07af8d8338e52fc2f51ee687100acd1ca2d6fd72813d861b4
- this leaf
- b740ae4670d9ec716635e85a3ba5e1126561b7d6c9f2f35650fc3337a79ed429
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /GBFBORFe/amAYt7goQ9Am/RHgd0CCCTlleGewxbkNFioTEpTq+r7I7n5iQQcF4JWmEl9WeSucGXwjc2B7V1CA==