Payment channels

BillPro channels can create a separate configuration and payment flow for different transactions. With Stripe, you process all payments in an e-commerce channel, even phone payments.

With CardCorp, you may have a phone-payments channel, as well as an e-commerce channel.

E-commerce channel

In an e-commerce channel, you accept payments with payment links, iframe checkouts, and the virtual terminal. For the virtual terminal, you must always use 3D Secure (3DS) authentication.

You can configure the payment links option for user accounts.

The e-commerce channel has the abbreviation ECOM.

Phone-payments channel

In a phone payments channel, you can accept payments with the virtual terminal. For phone payments in this channel, you do not have to use 3DS or enter the CVV.

But most issuing banks require 3DS when you are storing a card for recurring payments.

If you send a payment link after a phone payment fails, the payment moves to the e-commerce channel. In this case, you must use 3DS.

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. They indicate the payment processing workflow that BillPro has used. If you have more than one merchant account, each account will have a different channel. So you may be able to identify an account from the channel abbreviation near a transaction.

PCI DSS Level 1 compliance

In BillPro, merchants and customers enter card details 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.