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
- 65b4cc68168a2318621eec81f8fb087ea08e3db8289acdfa431306fa34fac10c
- request
- a10da881fb240cc6651a44d2f65c626227746045cdacdf2c3972abdbc4494972
- transaction
- ced4cdb9b70250729e451503d177e64e5246a336b04b8a0ba4e6b2e4b5c6a60acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74178
the chainentry 74178
- sealed to the entry before
- 5ca9822c8cdc56c576dc631999d6e0877c78f8419ab82a485cd96cedcbb4c57f
- this leaf
- 2ce7ad9c4a4bb6ae57c2e39eccae8e76abd06ae7c13ccefd2c1d03696365a6b2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bSyfBoePZe5nsgWXwuN6UOZwHiB/lGX1FGspBh5fZfS7W+EIJ7jlHBRB3j31ADDN3ir/h8IuBOOomVlvEefzAw==