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
- d69ab8032b67f8207c06888dbb41ff37de18f76c6f96808a5c216407e2c5d50b
- request
- 53b6fde0203987f1ef18b4a1fec3f361535a32c40bbb1aa0ef187b9bbd282cd1
- transaction
- de7b5571faec28734e4211a9db46b41b3d7004deb3b0a4a1ba0a80e195b8eaa5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5568
the chainentry 5568
- sealed to the entry before
- 25bb42fe462fe89a79c9a64be11fb5f9fdcd71aaae31d8d875c0f87c2e0fd00a
- this leaf
- 9023cae2966adf307cdb48bf13db30594e05e48c96ca54c77d493021fb0fb722
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bDyKC/olJbV2XNEfcxRONoFvmmbA0aAQ+vN9Ax1BQVoXpYFA4HIE3Og8ZrXvnlMlcofXXC5yoVDgyzHvHDtlBw==