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
- facc990cc5bddd80aea77f5df9aba803f8569dccd15084aed5b15f61c47c138a
- request
- c5012711d0ae30d050b0e74ab2247f98c8b4baf521179125763c90018198b890
- transaction
- 54078a883d20f2b1cfba469f79c24d62f7a726b1ccf62b945f00129267677d73computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23762
the chainentry 23762
- sealed to the entry before
- 73373c095eaa79c692f91e27948b0717e6644588710ba0a748196f22690cf2dd
- this leaf
- 5a4811d51cc66f1977e3ed9d0cbe51bbb5e98c29a4eaf2949399cb09261c0c9c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vkNw+RxLNO+d6OYGyte6nZ68DEk5SjPKxVhyufZEzNku9nZgk/zyp1ij3fl9lRi9P7BqgRuJAq85qR+6aZ9XAA==