Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Available tags Pronamic Pay WP plugin #364

Open
maikeldi opened this issue Jan 11, 2024 · 1 comment
Open

Available tags Pronamic Pay WP plugin #364

maikeldi opened this issue Jan 11, 2024 · 1 comment

Comments

@maikeldi
Copy link

Hi,

We're using the WP plugin in combination with the Payment Provider Rabo Smart Pay. Currently we're sending only the order ID to Rabo Smart Pay, this makes is difficult for the client to match the orders they see in Rabo Smart Pay with anything they see in their accounting software. Their request is to not receive the order ID but the name of the person who order.

However the available tags are limited. Is it possible to change the available tags?

image

@remcotolsma
Copy link
Member

remcotolsma commented Jan 11, 2024

We can add additional merge tags, but the Rabo Smart Pay merchantOrderId field is limited to 24 characters. It is also quite unusual to include the customer's name in the merchantOrderId field. Matching Rabo Smart Pay orders based on a customer name in accounting software also does not sound like a best practice. Shouldn't the {order_id} ideally also be visible in the accounting program to make it easier to match? We doubt whether adding a merge tag for the customer name is the best solution to the problem. Which accounting program does the customer use? There are no options there to make the {order_id} visible in the accounting software? With a few orders per day, matching based on customer name may still be workable, but based on an {order_id} seems more common to us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Status: In Progress
Development

No branches or pull requests

2 participants