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
- c065d128ca677e1dfe8ec226318b9a35f40d258ad3dcc16b1994c88b6ddacf62
- request
- 9996c6ffe20f31a697781346399ffa5e7e970fac8af46d2ed289d4681952ae86
- transaction
- d45d62d0ff635f7e2efc8cecbc6ddb10e9afdf7576ba32b67740f32cb037aa67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63240
the chainentry 63240
- sealed to the entry before
- a9bd28a4029580cf6f9babf05e9aa99d7d12ca6934fd7dc15869099881c55f50
- this leaf
- 5c4878d83e548091f9d99630f0996f06ea759caebd415fec89e19695c31d8ebd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gr+eLmSOx1OzMJmeNiGQ2dqr/3I1xJwRwv0Xr6YPwePld2csgve5EEoBqbRXnIO92d3yzeMYTC/gKdBwbKOrCQ==