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
- 2a8461d03676cd2c0958b34f4d723e7e206089dd9bd09195344ad28a7d9519b1
- request
- 8fecf021c6ee9c81cab290798b9ae9e7fbdf3f2dc4475c472a5faf8893b42329
- transaction
- f02fa008d31dacc955db4e094e644b3a294c934eae91c3f4bdb23df42f83a920computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32212
the chainentry 32212
- sealed to the entry before
- 64db8f1214536c09136e5555ea4376931be96366f79d2c541fd251853cdd4189
- this leaf
- d5bbdf3699e3d9689e5f0ad38d965b1db5c4f48bec85a3bf718633be34774453
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2brocxwXGQ/dOF0nIueQ5qX9q4v8U6mqMpAvcjCKv7nlXva0mTrB13vIpbJh6aqO7ew+dOJgbKDQeZTXRpqDCQ==