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
- 76779ea72ab915d826ad888aa4403fd66a69f9cf5561ab4a7489e4db808d866b
- request
- c4e442cd555f5e6ad0a9a2f07397aa8b03eb3225cf26a14f88dd3c4790b5d898
- transaction
- 6dc2e401937fcb67cf14dfa77cf083bc9d73d2ceac45e488ae7221a1f3a534d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72912
the chainentry 72912
- sealed to the entry before
- b7abf834b498b3e345cdad788d65d8a70b83e06a8bfcf212504d91022fea7bb1
- this leaf
- 7babb4fe569e708ac3f2a1ea50d0e6c24f98920e66016f3919e0885081cd5110
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +SmVUH1xs1Pjox5hVUGiT0mAt6U+TJlNx2RZRiRJSniFVlI44G2rnpk7kllV9VtfrkQIcGQKeHlOGyD6OQxXBQ==