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
- efe7f65a1052cbb768fb6f6baaddb26170fef493cdf9abb718544efd61884ae5
- request
- dc4976551d0e308298e856ecf74c2fdb2fb26a49752f9fbff029fdb5de17b063
- transaction
- ebd20cae7626dc55d146ea0521b679998d06256f4c435ab24f9bda4009e8af50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11418
the chainentry 11418
- sealed to the entry before
- d06ab601dbfa8608f6f8a487c836d38f3fd4120e8566b3882176ea410af64d6e
- this leaf
- 76fa093888d998881c7d041f01cb76586a6e9ae92638e9679b73bd014ab6bec8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3tUEbVL+j+mgQfPbFj3pcmkI0wsaD8nUIS3j501XBuaiIPE2APaH9ejrFD2Fv3BBzU9epi+QLngaK7j6Get8AA==