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
- 00f820617afd75f497a4e7acf4c54462f38c38dc179175b851286363702c0cfa
- request
- 3c05f2aa218704fb3c649dbc4ceb077ed46fe4db07e6323e492558a59f22018b
- transaction
- a88faffeb2b154b9be9f68e2a38bdfdce4b82b6e638b1906276b2d6150b0d294computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5074
the chainentry 5074
- sealed to the entry before
- d427a756ff0643b6e6dea7b0669b0b437db16c2b6ab290bd1288c3f2d4e8b903
- this leaf
- 01cfa92c9e4da6baae487abf63270a93990bc591cdff6bfb72661c4ef4ab5791
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hPi672gKCbZB0ZzvE/bNhk9Ctnjg9QiXcIdt2NMMyVJJKjxAEwD0c9QKFKtcN9kpA52fpj4FrisA85hkylksBw==