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
- 45ff43498fd72adffeb6252c95cba65352c263aed0c1acfcaff2b52e05b5f588
- request
- 0407ed6aed001a571f9fc99ae8cd6d66f69a7ee5efcc3c6215786b16c80b02ab
- transaction
- 521a3d5aafd8b7b3c571f974fee003ee4a5f28df95117db795dd38fe393b01a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56199
the chainentry 56199
- sealed to the entry before
- 7fd4af34a201240d9ae240959650672444b10951d086be3d0a3d042a9765ccb1
- this leaf
- bbed5c9c49db28bc95b2011366aedbeb2abc9de36236594b39cc4107c503f529
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ARMOVpfR0bNTLdfIDMu9iHO4yRHLtRTIdZlWjtC+T4gTbwHEHkdNKHDlgA1wg7HPwP4UVq/ZMQtkBOqvFseyDA==