<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic eCheckType on Payment Profile | WEB vs PPD  when using recurring billing and one time trans in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/eCheckType-on-Payment-Profile-WEB-vs-PPD-when-using-recurring/m-p/66263#M39826</link>
    <description>&lt;P&gt;I am trying to figure out a way to use one Payment Profile of a users bank account that will suffice for 2 flows in an application, one being the user selects his previously made Payment Profile and that gets used for the transaction and the eCheckType will be 'WEB', simple.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But the issue is we need the eCheckType to be 'PPD' when that user decides they want recurring billing.&amp;nbsp; They select the Payment Profile made above ( which is 'WEB' for eCheckType ) and continue, which is not what we want it to say.&amp;nbsp; Using the API to create this subscription w/ payment profile I can't seem to find a way to update the eCheckType on the subscription.&amp;nbsp; Do I need to update the eCheckType on the bank account first then do the subscription call?&amp;nbsp; But I assume that will mess up the eCheckType when the payment profile is used for a single transaction ( being ppd and not web that time around )&lt;BR /&gt;&lt;BR /&gt;When a Payment Profile was made, we tried making 2... one where the eCheckType was 'WEB' and then another 'PPD', both payment profiles had matching data except for the eCheckType.&amp;nbsp; The PPD payment profile came back with an error saying it was a Duplicate.&lt;BR /&gt;&lt;BR /&gt;Any advice on what to do?&lt;/P&gt;</description>
    <pubDate>Tue, 05 Feb 2019 19:31:41 GMT</pubDate>
    <dc:creator>nealdyrkacz</dc:creator>
    <dc:date>2019-02-05T19:31:41Z</dc:date>
    <item>
      <title>eCheckType on Payment Profile | WEB vs PPD  when using recurring billing and one time trans</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/eCheckType-on-Payment-Profile-WEB-vs-PPD-when-using-recurring/m-p/66263#M39826</link>
      <description>&lt;P&gt;I am trying to figure out a way to use one Payment Profile of a users bank account that will suffice for 2 flows in an application, one being the user selects his previously made Payment Profile and that gets used for the transaction and the eCheckType will be 'WEB', simple.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But the issue is we need the eCheckType to be 'PPD' when that user decides they want recurring billing.&amp;nbsp; They select the Payment Profile made above ( which is 'WEB' for eCheckType ) and continue, which is not what we want it to say.&amp;nbsp; Using the API to create this subscription w/ payment profile I can't seem to find a way to update the eCheckType on the subscription.&amp;nbsp; Do I need to update the eCheckType on the bank account first then do the subscription call?&amp;nbsp; But I assume that will mess up the eCheckType when the payment profile is used for a single transaction ( being ppd and not web that time around )&lt;BR /&gt;&lt;BR /&gt;When a Payment Profile was made, we tried making 2... one where the eCheckType was 'WEB' and then another 'PPD', both payment profiles had matching data except for the eCheckType.&amp;nbsp; The PPD payment profile came back with an error saying it was a Duplicate.&lt;BR /&gt;&lt;BR /&gt;Any advice on what to do?&lt;/P&gt;</description>
      <pubDate>Tue, 05 Feb 2019 19:31:41 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/eCheckType-on-Payment-Profile-WEB-vs-PPD-when-using-recurring/m-p/66263#M39826</guid>
      <dc:creator>nealdyrkacz</dc:creator>
      <dc:date>2019-02-05T19:31:41Z</dc:date>
    </item>
  </channel>
</rss>

