Is there a detailed list of supported payment methods?

Discussion created by asampal on Aug 9, 2018
Latest reply on Aug 15, 2018 by jeff.gross@vantiv.com

Like • Show 0 Likes0
Comment • 5

I initially asked this as a comment to the triPOS Cloud Overview page, but I think this forum is a better place for it.

We are investigating a potential integration with Vantiv (triPOS Cloud, specifically).

Do you have a comprehensive list of card-present methods of payment (MOPs) supported with the different EMV certified processors? I'm looking for something relatively comprehensive, e.g. see this list. We have also integrated with CardConnect, which offers a product similar to triPOS Cloud, and have found that the details around their support for specific MOPs are not always clearly spelled out. Since the set of MOPs which we can expect to be able to handle is dependent on the processor's platform support for the MOPs, the gateway integration with the processor (Vantiv's triPOS Cloud, in this case), and the terminal software (because hard-coded card AID and prompt handling might not allow for some MOPs), it's easy to see why there can be confusion.

We would appreciate any specifics wrt the above. TIA

Outcomes

jeff.gross@vantiv.com Aug 14, 2018 1:06 PM

Hi Adrian. The supported processors and hardware for triPOS Cloud are both defined toward the bottom of our triPOS Cloud Release Notes page at https://developer.vantiv.com/docs/DOC-2905, and in the case of each device and processor, all CVM's are supported (No CVM, Signature, Online PIN, and Offline PIN). Integrators can send a Sale request and amount to a triPOS Cloud lane, and then the PIN pad will prompt the cardholder to Insert or Swipe their card. From there, depending on the type of card and customer selections, the PIN pad may request a PIN or signature from the cardholder, and the card may or may not be processed as a Credit Card or Debit Card.

Actions

asampal @ jeff.gross@vantiv.com on Aug 14, 2018 3:22 PM

Hi Jeff - can I infer from your answer that the same set of MOPs is supported across all processors and that there is no variance? I was hoping for a more detailed list since I know that, for example, PINless debit as CP is not available on Chase's platform (directly) so obviously triPOS Cloud couldn't support that MOP with them, but it might with FD or your own platform as a processor. A similar situation situation could apply to other MOPs.

It would be good to know precisely what we can sell to our customers. If switching processors triPOS Cloud is pretty much transparent from the point of view of CP MOP support, this is a big plus.

Actions

jeff.gross@vantiv.com @ asampal on Aug 15, 2018 9:21 AM

triPOS Cloud doesn't support a true PINless Debit transaction in the typical sense (where the transaction is processed via a Debit network but without a PIN), but ultimately, if EMV is supported for the processor being used, the same CVM's and options are supported across all EMV-supported processors. This is the case because triPOS Cloud itself doesn't know which processor is being used behind our Express platform, so the functionalty triPOS supports must stay consistent across all processors we use.

Actions

asampal @ jeff.gross@vantiv.com on Aug 15, 2018 1:01 PM

I get that triPOS Cloud attempts to abstract the processor and provide a single API no matter the backing processor, but given that there are differences in processor platform features (e.g. the PINless debit support I just mentioned) and that your integration with each platform might differ in completeness of implementation, we had assumed we couldn't necessarily count on a set of MOPs to be available across all supported processors. I think you're saying that this isn't the case, especially if the approach you're taking is not to support a feature until all processors provide it.

Actions

jeff.gross@vantiv.com @ asampal on Aug 15, 2018 7:04 PM

When it comes to EMV functionality supported across our back-end processors, you are correct in that we support the same set of EMV CVM's and EMV functionality across all the processors where we have EMV currently enabled (i.e. Vantiv, First Data, Paymentech).

Actions

5 Replies

jeff.gross@vantiv.com Aug 14, 2018 1:06 PM
Hi Adrian. The supported processors and hardware for triPOS Cloud are both defined toward the bottom of our triPOS Cloud Release Notes page at https://developer.vantiv.com/docs/DOC-2905, and in the case of each device and processor, all CVM's are supported (No CVM, Signature, Online PIN, and Offline PIN). Integrators can send a Sale request and amount to a triPOS Cloud lane, and then the PIN pad will prompt the cardholder to Insert or Swipe their card. From there, depending on the type of card and customer selections, the PIN pad may request a PIN or signature from the cardholder, and the card may or may not be processed as a Credit Card or Debit Card.
Like • Show 0 Likes0
Actions
- asampal @ jeff.gross@vantiv.com on Aug 14, 2018 3:22 PM
  Hi Jeff - can I infer from your answer that the same set of MOPs is supported across all processors and that there is no variance? I was hoping for a more detailed list since I know that, for example, PINless debit as CP is not available on Chase's platform (directly) so obviously triPOS Cloud couldn't support that MOP with them, but it might with FD or your own platform as a processor. A similar situation situation could apply to other MOPs.
  
  It would be good to know precisely what we can sell to our customers. If switching processors triPOS Cloud is pretty much transparent from the point of view of CP MOP support, this is a big plus.
  Like • Show 0 Likes0
  Actions
  - jeff.gross@vantiv.com @ asampal on Aug 15, 2018 9:21 AM
    triPOS Cloud doesn't support a true PINless Debit transaction in the typical sense (where the transaction is processed via a Debit network but without a PIN), but ultimately, if EMV is supported for the processor being used, the same CVM's and options are supported across all EMV-supported processors. This is the case because triPOS Cloud itself doesn't know which processor is being used behind our Express platform, so the functionalty triPOS supports must stay consistent across all processors we use.
    Like • Show 0 Likes0
    Actions
    - asampal @ jeff.gross@vantiv.com on Aug 15, 2018 1:01 PM
      I get that triPOS Cloud attempts to abstract the processor and provide a single API no matter the backing processor, but given that there are differences in processor platform features (e.g. the PINless debit support I just mentioned) and that your integration with each platform might differ in completeness of implementation, we had assumed we couldn't necessarily count on a set of MOPs to be available across all supported processors. I think you're saying that this isn't the case, especially if the approach you're taking is not to support a feature until all processors provide it.
      Like • Show 0 Likes0
      Actions
      - jeff.gross@vantiv.com @ asampal on Aug 15, 2018 7:04 PM
        When it comes to EMV functionality supported across our back-end processors, you are correct in that we support the same set of EMV CVM's and EMV functionality across all the processors where we have EMV currently enabled (i.e. Vantiv, First Data, Paymentech).
        Like • Show 0 Likes0
        Actions

Is there a detailed list of supported payment methods?

Outcomes

Related Content

Recommended Content