We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
QuickPay can store custom fields such as CUSTOM_foo. See http://doc.quickpay.dk/paymentwindow/technicalspecification.html
It seems like that WordPay integration is support custom params (https://github.com/Shopify/offsite_payments/blob/d9453d0bc95ed272af10d9e5f088a04245a4d022/lib/offsite_payments/integrations/world_pay.rb), or is there any better way of implementing this? Perhaps what Authorize.net integration is doing? (https://github.com/Shopify/offsite_payments/blob/d9453d0bc95ed272af10d9e5f088a04245a4d022/lib/offsite_payments/integrations/authorize_net_sim.rb#L123)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
QuickPay can store custom fields such as CUSTOM_foo. See http://doc.quickpay.dk/paymentwindow/technicalspecification.html
It seems like that WordPay integration is support custom params (https://github.com/Shopify/offsite_payments/blob/d9453d0bc95ed272af10d9e5f088a04245a4d022/lib/offsite_payments/integrations/world_pay.rb), or is there any better way of implementing this? Perhaps what Authorize.net integration is doing? (https://github.com/Shopify/offsite_payments/blob/d9453d0bc95ed272af10d9e5f088a04245a4d022/lib/offsite_payments/integrations/authorize_net_sim.rb#L123)
The text was updated successfully, but these errors were encountered: