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
- 47081b195d040866c78ede901d0f4ee959459b6c625b4a221b5995fc2656a516
- request
- 42320634e443d931e130489d9de0bb83cb04773ff2112294671568b21a055676
- transaction
- bd2fc7a255c2459f724d9efb9ec211643967a8d99be44edca88d5e8d8bbaeac0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12525
the chainentry 12525
- sealed to the entry before
- fd68b0455890914d757998ee5eefa13bb4bdcfdd25fcf46c24bad2f705a1f61e
- this leaf
- 86a9be2e118d36bd1d6aa369abffcfe04489d2349b0ea8b04da380a460624e95
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qkVTkCogtlZ3B5AGyULsd1624kdNAjaqXL05asCWjn2T8DM7ci8T+GvtqfNiRmyQE0bZujs1uhVDPemf9piFDQ==