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
- 39b05c8e5df54bcbe5a7e670c6cd9b09942c65a3f678cc15493a2133b821657e
- request
- 4296683adef8a62dbfe462ffde331e6ff5d65f88a3827e70ff67c019c12a8956
- transaction
- 5197f63a796d52f8fad1ddeaa971784b9b8447547362e22c3a33798dc7020c1ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36784
the chainentry 36784
- sealed to the entry before
- 54e3a29092ef87399ac68482de90b56a7f63f4c983b97a161b44100a149ab339
- this leaf
- 0776a0d06145176451907b47f30697ceac96eab02ae7b45f5a3b101e3d0a2b0c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0YqCUSCmz0m79+gYAJNFy7mpOhzgROoc+lMSd1qVYEhb2EnZebaPH3pxWSvW3OQ0UVc0pX23zisUL1C6sDdgAw==