Closed (fixed)
Project:
Payment
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
19 Nov 2012 at 16:38 UTC
Updated:
24 Jul 2013 at 00:00 UTC
It'd be great if the Payment module supported DCC transactions. This is where you submit the card details and transaction details to the bank and they respond with the currency conversion rates they're offering. Then you do a second request for the authorization, again with the card details.
See https://resourcecentre.realexpayments.com/products.html?id=128 for the Realex payment gateway guides for their DCC XML API requests and workflow. Obviously we'd handle Realex support in a separate module, but to see how they implement it, it might be useful to look at.
Comments
Comment #1
xanoThis might already be possible. Every payment method can supply payment configuration form elements, which are shown when the user chooses a payment method that uses the controller to make a payment. When the user enters his card details, the validation handler (also part of the payment method controller) can trigger a form rebuild, which in turn executes a request to the PSP to fetch additional information. Then, during the form rebuild, different elements can be shown to the user, based on the results of the request.
Comment #2
stella commentedThat might work, assuming we still have access to the credit card details after the form rebuild for the second API request to the payment gateway.
Comment #3
xanoWhatever happens to form values is up to the payment method controller. By default, all data is simply kept in $form_state until the form is fully submitted.
Comment #4
xanoComment #6
xanoSee #2037081: Distinguish between amounts charged and paid.
Comment #7
xano