Hello everyone,
I've created a payment plugin in nop 4.6. at this point I need to save attributes for order but order is not yet saved in DB ( proccess Payment). Getting order by guid returns null. What should I do? I tried to do like PayPal but I got confused and it always return null for order.
Issue with creating new Payment Plugin
Сертифицированный разработчик
- 304
- 3032
- 28.03.2017
- Nepal
hshadmehr wrote:
The process Payment (used by on-site payment) method executes before an order is placed while the PostProcess (used by redirection payment methods) method executes after an order is placed so you can get the order by the GUID only in the PostProcess method.
What attribute are you trying to save? The checkout attributes and the selected product attributes are automatically saved when the order is placed in the Order and the OrderItem tables respectively.
Hello everyone,
I've created a payment plugin in nop 4.6. at this point I need to save attributes for order but order is not yet saved in DB ( proccess Payment)
I've created a payment plugin in nop 4.6. at this point I need to save attributes for order but order is not yet saved in DB ( proccess Payment)
The process Payment (used by on-site payment) method executes before an order is placed while the PostProcess (used by redirection payment methods) method executes after an order is placed so you can get the order by the GUID only in the PostProcess method.
What attribute are you trying to save? The checkout attributes and the selected product attributes are automatically saved when the order is placed in the Order and the OrderItem tables respectively.
- 21
- 105
- 21.01.2019
- United States
Yidna wrote:
I want to do that but saving attributes needs an entity to use it for getting the attribute next.
There is no order to get. The order is created later.
One way is to temporarily save the attributes as generic attributes the add them to the order when it is created i.e. use PostPaymentProcess
One way is to temporarily save the attributes as generic attributes the add them to the order when it is created i.e. use PostPaymentProcess
I want to do that but saving attributes needs an entity to use it for getting the attribute next.
- 21
- 105
- 21.01.2019
- United States
sanju.dahal741 wrote:
Api send me back a transactionId and two tokens for each request. And I have to keep them and use them until the end of payment proccess, all.
Hello everyone,
I've created a payment plugin in nop 4.6. at this point I need to save attributes for order but order is not yet saved in DB ( proccess Payment)
The process Payment (used by on-site payment) method executes before an order is placed while the PostProcess (used by redirection payment methods) method executes after an order is placed so you can get the order by the GUID only in the PostProcess method.
What attribute are you trying to save? The checkout attributes and the selected product attributes are automatically saved when the order is placed in the Order and the OrderItem tables respectively.
I've created a payment plugin in nop 4.6. at this point I need to save attributes for order but order is not yet saved in DB ( proccess Payment)
The process Payment (used by on-site payment) method executes before an order is placed while the PostProcess (used by redirection payment methods) method executes after an order is placed so you can get the order by the GUID only in the PostProcess method.
What attribute are you trying to save? The checkout attributes and the selected product attributes are automatically saved when the order is placed in the Order and the OrderItem tables respectively.
Api send me back a transactionId and two tokens for each request. And I have to keep them and use them until the end of payment proccess, all.
Сертифицированный разработчик
- 304
- 3032
- 28.03.2017
- Nepal
hshadmehr wrote:
Api send me back a transactionId and two tokens for each request. And I have to keep them and use them until the end of payment proccess, all.
In this case, you can use the session. Something like this
Move it to the order from the postProcess method and clear the session when done.
Api send me back a transactionId and two tokens for each request. And I have to keep them and use them until the end of payment proccess, all.
In this case, you can use the session. Something like this
HttpContext.Session.Set("yourSessionName", yourSessionValue);
Move it to the order from the postProcess method and clear the session when done.
MVP
- 11337
- 101097
- 22.05.2011
- United States
As mentioned above, Generic Attributes can be used to save temporary values. Use the customer as the entity. See example
\Plugins\Nop.Plugin.Payments.CyberSource\CyberSourcePaymentMethod.cs
await _genericAttributeService.SaveAttributeAsync(customer, CyberSourceDefaults.PaymentWithNewCardAttributeName, isNewCard, store.Id);
\Plugins\Nop.Plugin.Payments.CyberSource\CyberSourcePaymentMethod.cs
await _genericAttributeService.SaveAttributeAsync(customer, CyberSourceDefaults.PaymentWithNewCardAttributeName, isNewCard, store.Id);
- 21
- 105
- 21.01.2019
- United States
New York wrote:
If a customer has more than one order in proccess to pay, doesnt it make any ptoblem?
As mentioned above, Generic Attributes can be used to save temporary values. Use the customer as the entity. See example
\Plugins\Nop.Plugin.Payments.CyberSource\CyberSourcePaymentMethod.cs
await _genericAttributeService.SaveAttributeAsync(customer, CyberSourceDefaults.PaymentWithNewCardAttributeName, isNewCard, store.Id);
\Plugins\Nop.Plugin.Payments.CyberSource\CyberSourcePaymentMethod.cs
await _genericAttributeService.SaveAttributeAsync(customer, CyberSourceDefaults.PaymentWithNewCardAttributeName, isNewCard, store.Id);
If a customer has more than one order in proccess to pay, doesnt it make any ptoblem?