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
- cc7c3d7ef6232b4a3e773ec5465b3e67ecb55c60895ffefbf92b0021564d8dae
- request
- d78e1ab1173af38ee44f17b83f1e27d42cac0ca5e4a6c59ae290312e3b9955d1
- transaction
- 34e2bdc230785ec720329efa59b539422d31da783ee37efd14826a5f34f30c53computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49169
the chainentry 49169
- sealed to the entry before
- e17e56c7d32da58727dc805316d395b40338b95df02ff927fa8b8ad3bf67c98e
- this leaf
- 9d0395ee75eb22b20ca6519c4a9559a2be25ef9e099006afb94da7d5c14b25aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ceAaJtJH9XehLpQVNStUiJYkwL/XGr2vOAow5TFEu32qwxgW616PGwfsm58V4CiwDD8NP07upQB2+7tMGjwuDQ==