web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

2009 NAV R2: Credit Card Tables Stored.

(0) ShareShare
ReportReport
Posted on by 435

Good Morning,

 

I had a question regarding credit card tables in NAV, NAV is connected to a website we own that allows purchases from consumers. It also allows users who do-not have accounts to purchase items anonymously. We've noticed that NAV is saving the credit card information onto the table. I'm just curious.. Why does NAV do this, and is there a way (for security purposes) to disable or navigate around this? Thank you so much for your assistance with this! 

*This post is locked for comments

I have the same question (0)
  • Tony Hemy Profile Picture
    on at

    Jason,

    NAV does not store the credit card information on the purchase table, it is stored as an encrypted BLOB on a special table that is only decrypted when you send the transaction to the DO Payment Service

  • Jason_AnA Profile Picture
    435 on at

    we noticed that every time we RELEASE an order it add a credit card entry in the credit card table. I would like to know if we have a way of turning this behavior off.

  • Verified answer
    Tony Hemy Profile Picture
    on at

    Hi Jason,

    I think you might min-understand what is happening with your DO Payment processing.

    The Credit Card table is not populated with a new record every time you release a sales document, quite simply the table is not structured in such a way as to make that even possible.

    There are 3 main tables that exist for DO Payments.

    827 "DO Payment Credit Card"

    828 "DO Payment Credit Card Number"

    829 "DO Payment Trans. Log Entry"

    The relation between 827 and 828 is that 828 holds the encypted details (Credit Card number) for the record in 827.

    A record from 827 can be related to a customer and only one customer. When you specify that customer on a Sales Header it will allow you to select one of the pre exisiting credit card records on that sales header. When you process the payment request it uses that credit card and creates a new record in 829.

    The 827-828 relationship is an anomaly, however the rest is 3NF.

    You seem to be asking ALOT of questions around the Dynamics Online Payment Processing, however I am not convinced you have taken the time to look at all the existing information out there including documentation about how to use the functionality. IMHO you are jumping to a lot of conclusions that could be negated by understanding the functionality first. I wholeheartedly suggest you get the documentation and read it, play with it in a demo environment, and see if there are even any videos out there.  Then if you are still unsure about what is happening come back and ask some questions.

    t

  • Jason_AnA Profile Picture
    435 on at

    Thank for you Tony for your reply.

                We're currently working in a demo environment. Unfortunately what we lack is Documentation.. I've been doing most of my research in forums etc. If you know of any documentation I can review please let me know.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans