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
- 61b660710455f51f91677dc0b4fbbd963082d9268ad0352f5bb38071ae52c161
- request
- 18dab8f10577d8c39d70d21cb99be37f0d8ffa633399bc82c06e0492d726c6e6
- transaction
- b563b61877bd3f625540155c98eeb4f79df1accb7a0bce56abb10fe85b2c2666computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34569
the chainentry 34569
- sealed to the entry before
- bbfd80f84cc526ec94b5f4af2de87cd80d034595c0ab8fb1480d6def7a67072c
- this leaf
- a41c23f64f76f04305cea8e1dc28dd99fff454ab3cbbbe25226cb017583a7f40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- btJvLI+xpN2O6qaSE5y4T/UV08En+unL9P3FHqik1TALlJMLkhcV4oCzGI5hKHXHzQE8BGBIrakvcy6wQbCsBg==