<p>There are a variety of ways you can solve this depending on your needs.  </p>

<p>One possible way would be to assign users to groups and then use simple twig code to limit the shown payment options at the template level depending on which user (i.e which user of which group) is viewing the page.</p>

<p>In addition, some validation logic in a custom plugin should probably be used to prevent accidents in case a user does somehow submit a payment of a type you don't want them to be using.  However I don't necessarily see an ideal event to listen to for that - I'd check with Luke Holder but perhaps onBeforeSaveOrder would work - see <a href="https://craftcommerce.com/docs/events-reference#commerce_orders.onbeforesaveorder" rel="nofollow">https://craftcommerce.com/docs/events-reference#commerce_orders.onbeforesaveorder</a></p>

<p>Basically it comes down to how you'll be differentiating these users - without more info it's hard to provide a more substantial answer.</p>

CC BY-SA 3.0
2016-10-20T11:34:07.090Z
Im creating a custom plugin as a solution. Would be more secure i guess
Bram B
CC BY-SA 3.0
2016-10-20T05:31:16.620Z
2016-10-20T05:31:16.620Z
Jeremy Daalder
<p>Is it possible to allow certain payments per user in Craft Commerce and if so how and if not how would it be possible?</p>

<p>Just breaking my head around it.</p>

<plugin-craftcommerce><payment-methods>
Craft Commerce payment methods per user
# Craft Commerce payment methods per user

(Asked by: username_0 on 2016-10-19)

Is it possible to allow certain payments per user in Craft Commerce and if so how and if not how would it be possible?

Just breaking my head around it.

**Tags:** plugin-craftcommerce, payment-methods

---

## 1 answers

### Answer by username_1 on 2016-10-20. Score: 2 | Accepted answer

There are a variety of ways you can solve this depending on your needs.

One possible way would be to assign users to groups and then use simple twig code to limit the shown payment options at the template level depending on which user (i.e which user of which group) is viewing the page.

In addition, some validation logic in a custom plugin should probably be used to prevent accidents in case a user does somehow submit a payment of a type you don't want them to be using. However I don't necessarily see an ideal event to listen to for that - I'd check with Luke Holder but perhaps onBeforeSaveOrder would work - see <https://craftcommerce.com/docs/events-reference#commerce_orders.onbeforesaveorder>

Basically it comes down to how you'll be differentiating these users - without more info it's hard to provide a more substantial answer.

> **Comments:**
> **username_0**: Im creating a custom plugin as a solution. Would be more secure i guess  

---

