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
- eb7c22ff6dc37ffbdbca8ee1b034fa49fa189606215f476e62b423ce0b7c621d
- request
- de633022ca9f512c5b54522da3d19eab1a3f160faa07ea4f27c15d489269e524
- transaction
- b5ad1f67541ffdb2216228550f30c5eeabfe2074d1f99d16006d0faa0a19329fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45086
the chainentry 45086
- sealed to the entry before
- bfa551e4db0c4c52c572eeea3a26fea95b60168fc53e07e61eaa42fa801c631a
- this leaf
- 3af2cd72e37ff211f6055bbedc87302ce0188507100ca492645ef10e494bd024
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 54eQz680JtdS1gQH+Qd0zfZasczIXNDRiVkL6NTXMNwiE0vWSsBCid/g/xiCFCA9cN8ItH4SWtaR/VupGyFyDQ==