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
- 908b369598d89c4d8b0908cd83d88a3cad7dc158eac9f723a329268077415239
- request
- d99fd40207ba406730ecd1c3393aac58ddb52a71dd7bfc52498a40a01a2336b1
- transaction
- c852b1c34df9aad75c10d64496bdf11b833850c5c114acb77e655b27dab11c68computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1325
the chainentry 1325
- sealed to the entry before
- 9455cd4630aa224363673277e37924ce21cf068366753811875f16225bed6a3e
- this leaf
- d8836090e8bb3bc2c2c9fd93035c245afaf352ad15dc479c68b3b04ff3b7d6d4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 315P67IpYiSBAKX6BAwXAypswbhmftLwI3H+EwTyPgeBLXU+dYK8S3x2lAvcc/T++0uFTAN890IqQVvJQlZFDA==