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
- 4818bd84dd6b75a2faeef85b747ea76fcf4cfa21f2f3022cf5876c026a8e6689
- request
- 202b58710ae897b1afd14ff16a14eeeaaa89a5215bbaa6a7a674effb5663393d
- transaction
- f9954aafc52842c58def1463dcaabc4282a2f28a7e546a73a208f10e8d335714computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21995
the chainentry 21995
- sealed to the entry before
- 21be2b775915a46b7c05b7c6852fe322a9e3367be97394fc290a9fe8971f88a1
- this leaf
- c4b89f91db9ce151e3fdd5b6eb9f1624656d0b63dd98ebe166f7093d985030df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KsovW7WtrlAdwEVYUhqqcaSYj+SXBQbjQw+txF/2WuoxKgctYInldJvuOKXnMUmtPrQuBUDmhJ3DbR64uwxKAA==