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
- d461ce2071e4872d490a71980bdd8423b1634d06f6cc23509a30f7c122172c11
- request
- 6768934bf74bd8fd465e594402f05c6077867370a5837da7992de618ddc73877
- transaction
- a6a614fe42085fd64aeeddec1cfeaec492e49b3012f30cc88eb07744ab211235computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35212
the chainentry 35212
- sealed to the entry before
- 18b99441edc15f6ab52074d2f5b3ff459a2dace64595a1811f53c69527c58882
- this leaf
- 7f2d42b9aa0b7b267ce5c14f107544ea22b81964fce48a7cdb5e38a7b174f18d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ow4VD727FB5v59j1cYMDZBmWQakxbHcYWPTfcZApC/wEdZQesx6krXOHHgKPJXoW3SKwBOEgRE4FrFF4Mga+Dw==