Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>fixed. </p> <p>The fundingConstraint was causing permission errors. </p> <pre><code>&lt;fundingConstraint&gt; &lt;fundingTypeInfo xmlns=""&gt; &lt;fundingType xmlns=""&gt;ECHECK&lt;/fundingType&gt; &lt;/fundingTypeInfo&gt; &lt;fundingTypeInfo xmlns=""&gt; &lt;fundingType xmlns=""&gt;BALANCE&lt;/fundingType&gt; &lt;/fundingTypeInfo&gt; &lt;fundingTypeInfo xmlns=""&gt; &lt;fundingType xmlns=""&gt;CREDITCARD&lt;/fundingType&gt; &lt;/fundingTypeInfo&gt; &lt;/fundingConstraint&gt; </code></pre> <p>from the doco, Page 11 (bolded out for emphasis)</p> <p><a href="https://www.x.com/sites/default/files/2102_pp_adaptivepayments.pdf" rel="noreferrer">https://www.x.com/sites/default/files/2102_pp_adaptivepayments.pdf</a></p> <blockquote> <p>fundingConstraint New field: ap:FundingConstraint Specifies a list of allowed funding types for the payment. This list can be in any order. <strong>If this field is omitted, the payment can be funded by any funding type that is supported by Adaptive Payments</strong>. <strong>NOTE: This feature is available for applications with special permission level.</strong></p> </blockquote> <p>I was under impression that this was required by default (to make a simple payment) hence i was using it, but turns out it works fine and without it (so its kind of optional).A bit strange as I thought it should be other way around (special permission fro ANY type, no restriction for specified types) </p> <p>Also worth to note, when you create application don't be fooled by approval status ot check boxes under "Confirm funding sources you support". They (ECHECK, CREDIT CARD, BALANCE) were checked all by default, but it seems that regardless you would need a special permission as specified in APP creation process just bellow checkboxed items "<em>Changing default payment sources will require additional Review time and specific PayPal Approval.</em>"</p> <p>In other words, the app was not under 'conditional approval' which this note suggest.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload