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
- 94aac29f29d404a0f689d94a77ea27858533d3f55c9a4d6bb2f9cd85975dbe78
- request
- 684b89842dfeeb8bced6e5033deac4293aa56ea3e51cfbfef154d591e54e2129
- transaction
- 685681efc899667658244aa6df03eeae14143052f27e52f5dcb7411b25ed3369computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23685
the chainentry 23685
- sealed to the entry before
- bc37d282a712d7623b7562343c1bc800b0c843d3a8a368de953a1728fd09a171
- this leaf
- bf006df8d857b3cb22c694a8643a6a95493a46cbdd36ba479165e9a061aa71fe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B5zm86VuLCtgN3JWOFqeQZEaxhTWEVpkvVV5TVchQCk5S9mXVEW0/CskUNT7ogGPRPmCGgsmlhaVp8rXfl96Cg==