Use Purchase Order option to process certain payments offline

@tjaskolka,

That's exactly right. The following should cover what you're after:

{% if context == "checkout" %}<script>
function poRefresh() {
	requiresApproval = (FC.json.total_order > 1000 || FC.json.shipping_address.country != "US");
	FC.json.config.supports_purchase_order = requiresApproval;
	FC.json.config.supports_pay_with_plastic = !requiresApproval;
	FC.json.show_paypal_express_payment_option = !requiresApproval;
	FC.checkout.renderPaymentMethod();
}

FC.client.on("ready.done", poRefresh);
FC.client.on("cart-item-quantity-update.done", poRefresh);
FC.client.on("cart-item-remove.done", poRefresh);
FC.client.on("customer-address-change.done", poRefresh);
FC.client.on("customer-login.done", poRefresh);
FC.client.on("cart-coupon-add.done", poRefresh);
FC.client.on("cart-coupon-remove.done", poRefresh);
</script>{% endif %}

Paste that code into the "Add custom header and footer code" of your store's configuration section in the admin, to the footer textarea.

The code will then be inserted into the checkout for you, and will automatically update the payments section on page load, and whenever the address or cart total is altered to ensure it's always up to date with the current cart.

@tjaskolka,

Thanks for whispering that information. Update the poRefresh() function to look like this:

function poRefresh() {
	requiresApproval = (FC.json.total_order > 10 || FC.json.shipping_address.country != "US");
	FC.json.config.supports_purchase_order = requiresApproval;
	FC.json.config.supports_pay_with_plastic = !requiresApproval;
	FC.json.show_paypal_express_payment_option = !requiresApproval;
	FC.json.config.has_multiple_payment_options = !requiresApproval;
	FC.checkout.renderPaymentMethod();
}

@rthrash,

Good question. I'm assuming you're meaning that if someone looked at the source code they would see the flag that was necessary to trigger it? If so - you could instead use Twig logic rather than straight javascript which would obscure it a bit more. The twig template is still included within the javascript to allow client-side rendering, but it would be embedded within the template so would be a bit harder for the clever users to find it.

If you wanted to completely obscure it, you could send a request off to a secure endpoint on your side to decide, but that might be overkill for what you're needing.

@rthrash,

The secure endpoint would simply be a script you set up on your side, and then you'd set up an ajax call on the checkout that sends over the necessary information to your endpoint - which in turn responds if the user is enterprise or not. It'd be something you'd configure purely on the checkout.

For the Twig template changes - you'd basically approach what I detailed above but just within Twig logic instead. You'd overwrite the payments block and alter the needed variables. Something like this:

{% block payment_method %}
    {# logic to set is_enterprise here #}
    {% if is_enterprise %}
        <fieldset id="fc-payment" data-fc-container="payment">
            <legend><span class="fc-section-counter"></span> {{ config.lang.checkout_payment_method|raw }}</legend>
            <input type="hidden" name="fc_payment_method" value="purchase_order" />
            <input type="hidden" name="purchase_order" value="Custom value for Purchase Order" />

            <div class="fc-form-group">
                <div id="fc-payment-method-no-payment-needed" class="fc-container__grid--payment-method fc-payment-method--no-payment fc-payment-method col-md-8 col-md-offset-3">
                    <p>Custom message to show to the customer</p>
                </div>
            </div>
        </fieldset>
    {% else %}
        {% set config = config|merge({ supports_purchase_order: false }) %}
        {{ parent() }} 
    {% endif %}
{% endblock %}

You'd paste that inside the {% embed 'checkout.inc.twig' %}{% endembed %} tags in the checkout template. What it does - once you've added in the custom Twig logic to check if it's an enterprise user, is displays the purchase order option if it's the only one present, otherwise it displays the normal payment options - but removes purchase orders from being displayed. You'd still need to have some value or condition that the Twig can check against - but the logic to show that it's using that is slightly more obscured from view.