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
- 1ccbc256f5bbb0ef4199f340315de58a8c21d41e7d892f6fb0d7518f1198de24
- request
- 2cdc4227da9fc56ae691b8dd7eb89ac6ade92e9bc4fd6b0c7d956e1184f62be6
- transaction
- 5b157286f6c715d8a78b90c133864210e84cd04a2078a9e499b5cce6564ef9cacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56313
the chainentry 56313
- sealed to the entry before
- 2b447f6b6e63e932fae5c21111bde475b93e54f7af8c822c17fbacd0e11d598a
- this leaf
- 3f7cd974a7056f01eb584d134dc9e90f27c2f680859e3be13a1d375f87bae20f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pmO0hZIUekDl/LJVBzplkHvASL1QqZ4/616J5TjbHkRXAZuTwnbt7bGNFYWnRkSBx6fmNY1uKAvMHIbIDHzpDQ==