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
- bdf722ebca8132870e3e0e1a9bd736ee9cfa5cb5e8245e93b6f6a11845c07236
- request
- e9c8e472f790941c11dc259fe3499ac336e012401525e3eeae40b34990438b16
- transaction
- 28481089319084ce195e20c214e1256dbf2ba8579010234032fc65db86dd4329computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12395
the chainentry 12395
- sealed to the entry before
- 8273a45a67da9d274db20f83befe965c3dafc30645f460625239393b57cda366
- this leaf
- ce3a74a5c529882c5215394f0294fb3e582bfbcc52b38996ab63ccb8b68df024
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hGZXYy9Hay8BtmH9p+iCAFx4PFW4s7cyOB0GVyotfzlcvlEb/MXKKWGFK7IPhg2tU8Pg5eIiI2CeISvta96OBA==