By default, Helcim merchants cannot send full card numbers, expiry dates or CVVs via the API. This is to reduce the security scope and PCI-DSS compliant requirements of our merchants. Instead, we encourage merchants to tokenization card numbers using the Helcim.js tool.
Merchants can request permission to send full cardholder information if their unique integration needs require for this. If you want to send full card numbers through the Helcim API you will need to do the following:
- Contact Helcim to review your business needs BEFORE signing up for Helcim
- Once you have spoken to Helcim, you can proceed with completing your sign up
- After signing up, read, complete, and sign the PCI SAQ-D within 90 days. Your dashboard will start to remind you 45 days after your account activation.
- Once complete, the SAQ-D needs to be uploaded to the dashboard in your Helcim account
The SAQ-D must be completed, signed and uploaded annually. You will be responsible for complying with all of the obligations of the SAQ-D, for example arranging to have your network scanned. Please also note that AVS information will be mandatory for all transactions.
If your Helcim account configurations allows for full cardholder information, below are the API POST fields that should be sent in lieu of the cardToken and cardF4L4 fields. These can be used for "purchase", "pre-authorization", and "verify" transactions.
|cardHolderName||string||The cardholder full name.|
|cardNumber||string (13-16 length)||The full card number, which can vary between 13 and 16 digits based on the card type.|
|cardExpiry||string (4 length)||The card expiry date, in MMYY format (total of 4 digits without spaces or slashes).|
|cardCVV||string (3-4 length)||The card CVV (3-4 digits on back of credit card). American Express shows this number on the front fo the card.|
|cardHolderAddress||string||The cardholder's stress address.|
|cardHolderPostalCode||string||The cardholder's postal code.|