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
- 4c692ef176be5b2cda37e35671669e8b79914ac70cf6b7fe0d6248986276de38
- request
- d558e5ae1465c5391cb40e98acf3bbc97fa95167a5481988199e277ce1c0dfa9
- transaction
- 5af26a8a53bd821c0ab64920f3706b28b944694655a48983e9cae234f23d9ed8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51449
the chainentry 51449
- sealed to the entry before
- bdb868710cbe6eaafcd8ae343b3ccc947c480331fa33ba9c71869259cde1491a
- this leaf
- a49848c837ecea5a101a81795f7950fe1711fd052c7a046f8afd3ea47b904983
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2h9CbZXZIHU7Cx/67wGFTb3uVCkPx25vgYkZ08LyiQx5pFZhQeml03lJLIx9eNsdpGSz9P0boio5rxVP1+erCg==