Payment channels

BillPro channels can create a separate configuration and payment flow for different transactions.

• With Stripe, you will process all payments in an e-commerce channel
• With CardCorp, you always have an e-commerce channel, and you may also have a phone-payments channel

E-commerce channel

In an e-commerce channel, you can accept payments with Payment links and iframe checkouts and with the Virtual terminal with 3D Secure (3DS) authentication always required. (Note that you can activate or deactivate the use of payment links for individual user accounts. See Manage users). In BillPro, the e-commerce channel has the abbreviation ECOM.

Phone-payments channel

In a phone payments channel, you can accept payments with the Virtual terminal. By default, in the phone payments channel, the virtual terminal doesn't require 3DS, and when you enter a card, you do not have to enter the CVV. (But note that most issuing banks will require 3DS when you are storing a card for recurring payments). If you send a payment link to the same customer, the payment will be processed in the e-commerce channel, requiring 3DS. In BillPro, the phone payments channel has the abbreviation MOTO for "Mail Order Telephone Order".

Channel abbreviations

The channel abbreviations of ECOM and MOTO display beside transactions and provide information about which payment processing workflow BillPro has used. If you have multiple merchant accounts, you may be able to identify the transactions processed for each account by the channel abbreviation.

PCI DSS Level 1 compliance

In BillPro, merchants and customers enter card details directly into the payment gateway iframe. The payment gateway has PCI DSS Level 1 compliance. BillPro does not process or store sensitive card data. BillPro displays masked card numbers and stores tokens to represent the cards that are stored in the payment gateway