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
- fd8d61534fc86d8eb7469df333eb1b36389eb8ff3e19866226c3fe840bd794c8
- request
- 91ed3bf029b4fb8a6914f77a044e0175146a2a28b54202966a8a3e9887043e73
- transaction
- 858bc0bc149318df402a06644d8305598e8edc4468071f9faf6945a9ee6d4330computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26601
the chainentry 26601
- sealed to the entry before
- a32e300858317578ef3d9b6432da649862b906425adc91a643765a7c606dcff5
- this leaf
- 5b7ed3796bc1455bfe2fd518bc05fdb56969d7276068b08498b17a264e433966
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mLfN7RQBf958GLocUYxTURVx9LzSSpCMiwx5AEp+pdMXPg3roL81sPBn+UTXDCtgLq19FfFFO5J6JPeWjKMEAA==