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
- 93aae5c21d39d12ae58714d8a9279fa2cf4015f466b9f6bbe531bd81fb2a9c67
- request
- 009489f0da3a79c5b51e6a38f60cbb071b931a192667cb29df02d1b1b1e8f65f
- transaction
- 7eb362e1c3980d047968086ff5737c6c5025b8d2b136bf0a473cdcee8233b0decomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43102
the chainentry 43102
- sealed to the entry before
- c263a3db9d3dab0981141ac5054cc496e52adb215524042ec7fa0a5e27ff4997
- this leaf
- cfde94b2e843030985e98f7f95a8371a79750f9e5a5cb9e5ce4fb4edeae5394b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h+g8kzCdAnKzYdsuKCaL/iWW8mkN9EnPrL2zD094+KKAP39z4JnR2jHKXlgaYdscvWrJlWuTiuqcpPPbTayIDg==