Supply chain | Supply Chain Management, Commerce

Linking an infocode to card payment method

(0) Share

Report

Posted on by Liese-Marie Heyns

337

We are looking to build a solution for our customer who caters to a B2B customer audience whereby the Sales invoice is printed when a sale is concluded in POS.

I was thinking of creating an infocode that pops up and asks if the user wished to print an invoice. The user then selects Yes or no and we link a business event to the creation of an infocode transaction where the value is Yes.

Now I am trying to figure out where to link the infocode. I did this on the Functionality profile, on the operation "at end of transaction". But this then pops up when you use the option to edit and order and select "Pay balance later".

I only want the infocode to pop up when payment is taken - and the invoice posts. So i was looking at linking it directly to the payment methods in a store. However here you get an error "Reason codes cannot be defined where input is required for payment method with card setup."

0451.Screenshot_5F00_1.png

Can someone help me understand why I cannot link my infocode to a card payment method?

Also, is there any advice on where might be a better place to link my infocode? I tried looking if an infocode cannot be linked to a specific button, so I can link it to the "Conclude operation" button for example, but I couldn't find anything.

Thanks for any assistance.

I have the same question (0)

All responses (5)

Answers (0)

WillWU 22,361 on at

Like (0)

Report

Hi Liese-Marie Heyns,

How did you set up the infocode?

Please check the following blog:

community.dynamics.com/.../info-code-setup-in-dynamics-365-retail

Was this reply helpful? Yes No
Liese-Marie Heyns 337 on at

Like (0)

Report

See screenshots of my configuration below

Was this reply helpful? Yes No
Suggested answer

Ramune on at

Like (0)

Report

Hi Liese-Marie,

some information for this thread:

1. Info codes are not supported for eCommerce.

2. Functionality profile that allows to associate an info code to certain operations/user-actions are ONLY available for POS.

3. Rest of the info code associations are supported only for POS (e.g., info codes for customers/products/payment methods etc.)

4. Info codes for POS (not online store) –

a. Can be associated with a payment method through channel configuration

b. By default – it can either be printed or not printed – but it cannot be conditional based on user input

That too, only ‘Printing’ – info codes prompts & user-input

5. Info-codes don’t have default abilities to control the ‘Print’ of a transaction receipt – that would be a generic receipt prompt, in general without any info code involvement.

6. Lastly, there’s no receipt prompt/format association for different payment methods.

Was this reply helpful? Yes No
Suggested answer

Shafeeque P. 6,533 Moderator on at

Like (0)

Report

Please note that only customer info codes can be printed on the receipt. If the info code is attached to the customer and you have enabled the print settings in the info code config page, you need to add the "Customer Infocode" field to the footer of the receipt design.

Was this reply helpful? Yes No
Alex Hart 18 on at

Like (0)

Report

I see where you're coming from. Linking an infocode to a card payment method can be a bit tricky due to the error message you mentioned. It's likely because the system restricts certain interactions with card payment methods for security reasons.

To achieve your goal, you might want to consider linking the infocode to the "Conclude operation" or a similar button as you mentioned. While it might not be directly tied to the payment method, it would still provide the opportunity for the user to decide whether they want to print the invoice before finalizing the transaction. This can help ensure that the infocode pops up at the right time.

Additionally, you could explore custom scripting or extensions if your POS system supports them. This way, you can tailor the behavior more precisely to your requirements.

I hope this helps! Good luck with your solution for the B2B customer audience.

Was this reply helpful? Yes No