Checkout page from API Payment Link that does not REQUIRE the “Contact” (customer) information

Is there a way to create a checkout page using the Checkout API Payment Link that does not REQUIRE the “Contact” (customer) information? Using the Virtual Terminal does not require this.

We have commercial customers who pay invoices by sending us a virtual credit card.
We are creating Payment Links using the Checkout API from our internal system with the payment amount and our invoice number.
An employee at our company will enter the CC information on the checkout page instead of using the Virtual Terminal page.

Unlike with Virtual Terminal, the Payment Link checkout page REQUIRES “Contact” information (mobile phone number, email address, and first and last name).

There are a few problems with this:

  1. The payment information we receive from our commercial customers does NOT have an email address OR mobile phone number (and there is no “first name”).
  2. Even if we had a customer mobile phone number, we don’t want a 2FA message being sent.
  3. If we put in a “fake” phone number and choose “Guest” to avoid the 2FA, Square appears to “remember” the phone number and does NOT show a “Pay” button the next time.

Is there any way around this or is there an alternative way to create a checkout page without the required contact information?

Thanks. Mark.

With the Checkout API there isn’t a way to avoid the customer information. The digital cards that the companies are issuing you are they being used for recurring payments? If so have you looked at saving the card on file with the Cards API and then using the Payments API to charge them?

Also if you’re looking to build a very simple solution for employees to input payments you can use the Web Payments SDK. The SDK doesn’t require any additional information other then the card information. :slightly_smiling_face:

The digital cards are one time use. No need to keep cards on file.

I will look into the Web Payments SDK. We were just going with the Quick Pay API because of the simplicity in integrating into our system along with the additional level of security by having another level of “separation” from our system.

Is using the Web Payments SDK considered the same “risk” from potential credit card fraud and same PCI compliance as using the API to create a Payment Link?

Thanks. Mark.

Okay, makes sense. The payment links uses the Web Payments SDK too process payments. So same level of security. :slightly_smiling_face: