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
- e58d995454a66b4f7ef2ad8ca8bdd36af56c5586972100a99c3c607182da457f
- request
- 44ba57d5c18964b7167431ecdc9bb144ec6601f18e55ed4d252389ea402f19b3
- transaction
- f2e7aee77a72da10b601e81e8ea7b1404178726af146a90eeff69c43c311fee6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24301
the chainentry 24301
- sealed to the entry before
- fff12b0a79979b7432b568bf550ad75e873857832bfadca71da5fa23fa93fbb4
- this leaf
- 761dfee7d4b637f3b8ac0b4a133fcff3081d3286445631e2ed66c2e722a110b7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E3WFjXOiE7fZtglVA4TwIDloYmqFIa00kgJAJeSLzLdxZQW7qFPbRaHwaYri/saRKEjLUyvRKLBT9jYaMqDwDA==