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
- 53e75c2d3b5f83a037165ff998c43c01bd84fed20e7eb68e45941c78d0abe96e
- request
- 806fce0ac2429dc912623193518aab1c39e831993cc4ef8850488c886d19b5e0
- transaction
- 5196fa2fe0b9657c18eb67a33caa7b2463e1d04a1d5e56ce723ff930cfb34dd4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2827
the chainentry 2827
- sealed to the entry before
- 4871d2d6587be759d9f1761eec0729a6efdc4e286abc7a8ff339bbcdd56009a2
- this leaf
- 81d675ab0e324b14cdebee6a4f50074d0d591fd8c19849254090c344519c36aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZS/eiA9vy+RBgeFeTrFXYXvIqYNCMEz6t0pB1CZfA8WQ3U0rgaMdxt27Hlb9d0fghzpRxRlcCgtf1NLKXd0XBA==