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
- 6f6eb75b0e2a9ff2f83050e32e8114221e042294aef8706c69ef7f93b24cb70b
- request
- ff642d6513c98c0bdb933a4a88837538f3afd8d89ecba1efadcfff6bd09edd80
- transaction
- cd0c6c990f8dd5daeec20da3e4cfd28fa5a42070a9bd582ac26d4745a55a8bcacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27224
the chainentry 27224
- sealed to the entry before
- 37f020452b914b69942e5183c083428d8e309217d007fccd6916e0849ba2a885
- this leaf
- 222767276638f32e862813f19d9266f956ac732a3babd8bc028441e9fcc93e0d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g0gUk1U0SLIaVNb5Qx/IOgU5esBoGGZKDJo6QZiMy5zcVkA4h9aMMqF1tfvboq5mKMFVBaVV3TEkacVFktvMCA==