#Chhay Toch-client-secret-storage
thin cairn
Great! So we don't need to Create Subscription each times when the user come back to carry on their payment.
And one more thing,
Currently, I am store the PeriodStart & PeriodEnd to handle the expiration of the user accessible.
Should be do the Data Encryption for PeriodStart & PeriodEnd?
pulsar parrot
So we don't need to Create Subscription each times when the user come back to carry on their payment
You don't need to nope!
Should be do the Data Encryption for PeriodStart & PeriodEnd?
Not sure I understand the Q? Encrypt where
thin cairn
> So we don't need to Create Subscription each times when the user come back to ...
Currently, I am store the PeriodStart & PeriodEnd in the Database
UserSubscription Table
id
userId
periodStart
periodEnd
priceId
productId
subscriptionId
invoiceId
now, the field periodStart & periodEnd store as the Number.
pulsar parrot
I guess that's entirely up to your integration whether you encrypt them or not!
thin cairn
so if s.o access DB and change that field, it will be the problems.
thin cairn
I guess that's entirely up to your integration whether you encrypt them or not!
I would like to hear some advice from you, boss!
pulsar parrot
I guess it depends on how often you plan to read/write from those DB columns
thin cairn
Ok boss