#jakel-transfer
hasty prairie
no, you can't use the on_behalf_of param when making a transfer
on_behalf_of controls who the merchant of record is from the card network's perspective for the charge
rose topaz
got it
hasty prairie
if you're making a transfer, that's already happened - there's nothing to be on behalf of
rose topaz
would you recommend removing source_transaction on this transfer then?
We have GBP balance, and are attempting to transfer GBP to the UK connected account, but receiving this
hasty prairie
well, but presumably that gbp balance did not come from that transaction
if it was a eur transaction
so yeah - to make the transfer as described, you need to remove the source transaction param
rose topaz
got it. it looks like it was attached to the GBP payment tho which is a bit odd
hasty prairie
did that payment get FX'd to eur?
if you created the payment without the on_behalf_of param, it'll get FX'd to your platform's currency
hasty prairie
ok so - the "real fix" here is to have used the on_behalf_of param when creating the original charge
but for this specific situation, you'd need to just push forwards by making the transfer without the source_transaction param
the benefit of using on_behalf_of when creating the charge is that it's more FX efficient. you'll never do 2 FX conversions on the same charge that way, whereas you can (/ did) in this case
rose topaz
got it. we are testing the integration, so it sounds like we will want to use the on_behalf_of when creating this initial charge
hasty prairie
yeah - if you know that you'll want to create a transfer to a specific destination, it's generally cleaner to use on_behalf_of
rose topaz
thank you very much - i will work on making these adjustments and hopefully that does the trick!