Honestly looks like a credit card processor is being strange and publishing the card number in the wrong field. Only a couple people using the service had this

Honestly looks like a credit card processor is being strange and publishing the card number in the wrong field. Only a couple people using the service had this error (not caused by them). This has been fixed long ago, just this was a cached paged caught from beta.