#javier-1234_api

1 messages ¡ Page 1 of 1 (latest)

haughty muskBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1293924551884804189

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

small folio
#

Hello

#

Did you read through the documenation I shared in the previous thread?

lusty cairn
#

yes

small folio
#

Ah you are asking a separate question about supported bank

#

Yes I believe Banamex is the bank that is used here to receive these Bank Trasnfers.

lusty cairn
#

I can't find the list of banks that can send Stripe to Mexico? Where is that information?

small folio
#

You don't have control over that.

#

We don't really list that out.

#

Since it shouldn't really matter -- it is just a virtual account number that the customer will use to send a bank transfer to Stripe

lusty cairn
#

ok

#

curl --location 'https://api.stripe.com/v1/payment_intents'
--header 'Authorization: Bearer {{....}}'
--header 'Content-Type: application/x-www-form-urlencoded'
--data-urlencode 'amount=1000'
--data-urlencode 'currency=mxn'
--data-urlencode 'customer=cus_R0Mr0bRq7BKHr0111'
--data-urlencode 'confirm=true'
--data-urlencode 'payment_method_types%5B%5D=customer_balance'
--data-urlencode 'payment_method_data%5Btype%5D=customer_balance'
--data-urlencode 'payment_method_options%5Bcustomer_balance%5D%5Bfunding_type%5D=bank_transfer'
--data-urlencode 'payment_method_options%5Bcustomer_balance%5D%5Bbank_transfer%5D%5Btype%5D=mx_bank_transfer'

#

Is this the correct configuration to create payments in spei?

small folio
#

Don't believe you need payment_method_data there if I recall

#

But really the best thing to do is test it out

lusty cairn
#

If I don't put that information, an error appears

small folio
#

Ah you are right, I forgot you aren't confirming client-side here.

#

So yeah in that case you do need that parameter

lusty cairn
#

For payment attempts in Oxxo and Spei, should it be confirm=true?

small folio
#

Yes confirm: true is what actually initiates the charge process

lusty cairn
#

I mention this because for card payments, confirm=false, since the payment is made through the Stripe widget, in short, the payment is asynchronous.

small folio
#

Yeah with card you would have to already have created the PaymentMethod to use confirm: true

#

So that would be for something like a recurring (off session) payment using a saved card

lusty cairn
#

Ok, so use for spei and cash, confirm=true, that only creates the information to make the transfer in the bank, I understand that when the payment is made I will receive a payment.succeed event in webhook? Can the payment reference time be extended for oxxo and spe?

small folio
lusty cairn
#

is neccesary send return_url for spei and oxxo ? because only important the CLABE

small folio
#

Yes, return_url is required if you are confirming server-side

lusty cairn
#

in my case is only backend

small folio
#

Yep then you do need to set return_url