#Davaogoods

1 messages · Page 1 of 1 (latest)

coarse rampartBOT
eager tartan
#

hello! can you provide slightly more context? What charge type for Connect are you using - destination charges / direct charges / separate charges and transfers?

graceful wharf
#

transfers

#

this is a sample

#

I want to add our Fee to be reflected on that spot

#

when I do a transfer

#

to a destination connect account

#

any object I can set from here?

eager tartan
#

are you not collecting payments at all for your business model?

graceful wharf
#

we are for standard

#

but when the customer pays to the platform not the standard/direct

#

we need to apply fee when we do the transfer as per my first screenshot

#

this is so the connect account will be able to know that the transfer has a fee which will be charged to the connect account

eager tartan
#

to clarify, the customer pays the platform, then you do a transfer to the connected account right?

#

will you only transfer to one connected account?

graceful wharf
#

we do the transfer

#

"will you only transfer to one connected account?"

  • yes that would be 1 per connected account
eager tartan
#

and define an application_fee_amount when creating the PaymentIntent

#

this way, the corresponding py_ object on the connected account will show the fee

graceful wharf
#

then it would not be a transfer object correct?

eager tartan
#

a transfer will automatically be created

#

try it out

graceful wharf
#

will it reflect from here?

eager tartan
#

yes, the transfer will reflect on your platform account also

graceful wharf
#

hmm ok let me test it out

#

just to clarify this is when we do transfer correct?

eager tartan
#

when you create a payment, the transfer will automatically be done

graceful wharf
#

this is the code we used for transfer

#

so just to clarify I will replace this with destination charges object?

eager tartan
#

yes

#

but to be clear, the payment collection will be done using that PaymentIntent also

graceful wharf
#

got it will test it out now

#

it did not went through

#

and it is recorded on the main payment

#

it should be on transfer

eager tartan
#

the payment is incomplete, did you collect the payment method or pass in a payment method id?

graceful wharf
#

can show me refference to that

eager tartan
#

maybe can you paste the PaymentIntent id here too? let me take a look at it too

graceful wharf
#

here it is

eager tartan
#

the PaymentIntent id in your screenshot that starts with pi_

graceful wharf
#

oh wait

eager tartan
#

i can't copy the id from a screenshot, so if you can, please paste that id here

graceful wharf
#

pi_3Ll2C5KhLpImRHOf126QoMpm

#

pi_3Ll2AnKhLpImRHOf1AhKnU5k

#

Im doing this on test mode

eager tartan
graceful wharf
#

I set it to card

#

as noted here

#

im having an error

eager tartan
#

did you include payment_method=pm_card_amex_threeDSecureNotSupported like i mentioned earlier?

graceful wharf
#

testing now

eager tartan
#

@graceful wharf what do you want to clarify about the transfer object?

graceful wharf
#

hi

#

I created a transfer through this

#

it processed but the platform was charged again by stripe fee

#

while if using transfer object. there is no fee charged

#

can i use transfer and apply an application fee amount to that transfer?

eager tartan
#

a transfer is essentially moving the funds. If you want to apply an application fee amount to that transfer, then you would just transfer less. There's no application_fee_amount parameter to apply to the Transfer object

If we're talking about showing the application fee on the corresponding payment object, then like what i said previously, you would want to use a destination charge instead.

graceful wharf
#

but if we use destination charge, there would be a stripe fee correct?

eager tartan
#

whenever you accept a payment from a customer, there would be a Stripe fee

#

you are accepting payments from customers on the platform right?

graceful wharf
#

but its not a payment from the customer, its a transfer/payout to the connect account

eager tartan
#

maybe lets clarify this first

#

where are the funds to transfer/payout to the connect account coming from?

graceful wharf
#

from the platform

eager tartan
#

and how is the platform getting that money?

graceful wharf
#

through the customer purchasing

eager tartan
#

alright, are you creating a PaymentIntent on the platform when the customer purchases something?

graceful wharf
#

1.) Customer Pays

  • Item 1 = from connect account 1
  • Item 2 = from connect account 2
    2.) Platform Receives the payment since those are 2 different accounts
    3.) Platform does the transfer to the account 1 and 2
    - Using transfer object = No Fees for transfer , but platform needs to charge them Platform Fee
    • Using Payment Inten = Works but stripe has fees, platform also able to charge Platform Fee
eager tartan
#

okay, so you need to transfer to 2 different connected accounts from a single payment

graceful wharf
#

+yes

#

we already achieved that using transfer object but with no platform fee

#

if we just take away the platform fee. from the transfer it would not reflect on the connected account why the recieved is deducted

eager tartan
#

then ignore whatever i said about destination charges. Using Separate Charges and Transfers is correct. If you as the platform want to charge them a platform fee, then simply transfer less

#

you can add metadata or a description on the corresponding py_ object

#

to indicate what's the platform fee

graceful wharf
#

can you point me to that refference?

eager tartan
#

after creating the transfer, the response destination_payment will contain the py_ object that you would update with the corresponding description and/or metadata

graceful wharf
#

which is where for the fee?

eager tartan
#

you would explicitly state how much the fee is that you're charging

#

none of this is automatic

#

it's not possible to display the fee on the Transfer object (i.e. the place where you've pointed out in this screenshot before) when using Separate Charges and Transfers

#

so the workaround here is for you to explicitly inform the user by passing in a String in the description , or key-value that mentions how much the application fee is in metadata of the py_ object

graceful wharf
#

oh

#

ok let me test it out

#

so basicly deduct our fees from the transfer and update the description

eager tartan
#

yes, that's right!

graceful wharf
#

is there a way to define the description upon transfer?

eager tartan
#

no, unfortunately not

graceful wharf
#

aha ok got it. I will play around with what you have shown