#moritz_api

1 messages ¡ Page 1 of 1 (latest)

inland lavaBOT
#

👋 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/1354087389550608466

📝 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.

ancient wigeon
#

Hi, I already posted some questions last week and would like to follow up with a bunch of questions. Going to post them now:

Following up on our previous communication, we appreciate the confirmations you've provided:

  • Existing VBANs created via the Sources API will remain valid after the API sunset.
  • Customers can continue transferring funds into these VBANs.
  • Once migrated to Payment Intents, the original source attached to the customer will be "consumed."

We now have additional assumptions based on recent internal discussions:

  • After the Sources API shutdown, if a customer transfers money via their existing IBAN for a payment created via Sources API, the funds will go into the customer's Stripe balance since there is no Payment Intent to reconcile against.
  • To continue receiving events like payment_intent.succeeded for payments originally created via Sources API, we would need to manually create Payment Intents.
  • If we do not manually create Payment Intents for these legacy payments, the received funds will remain in the customer's Stripe balance and will be applied automatically to the next available Payment Intent.

-> can you confirm our assumptions?

plush laurel
#

That sounds correct based on the reconciliation logic described here:

By default, Stripe automatically applies any available cash balance to PaymentIntents and invoices that are awaiting funding.
https://docs.stripe.com/payments/customer-balance/reconciliation#cash-automatic-reconciliation

As mentioned previously if you want full control over this you can switch to manual reconciliation and use the API to apply customer balance to payments intants & invoices as you receive events indicating available funds:

Stripe sends the cash_balance.funds_available webhooks to your server to notify you when there are new funds that need your action. When you receive the event, you should decide which payment, if any, to apply the balance to.
https://docs.stripe.com/payments/customer-balance/reconciliation#cash-manual-reconciliation

inland lavaBOT
ancient wigeon
#

is there a chance that we switch off the Sources API in Test environment only? That would make testing way more easy?

plush kelp
#

As in just start testing with the payment intents API in test mode? If so, yes. Test and live are completely separate from each other, we don't enforce things in live mode because of how you test

ancient wigeon
#

no I mean shutting down the Sources API, to test our migration and simulate the sunset of Sources API

#

We would like to test what happens if we do not receive the sources events anymore.

#

We are currently writing a scrit to create a payment intent for all open sources payments

plush kelp
#

Good question. Do you know if this aspect of the sources API was extended on your account in some way? I don't think it is generally possible to shut off the sources API in general, though I do know some have already been sunset

ancient wigeon
#

We have until 31st of March (officially). Unofficially it is probably available a bit longer. We deploy our changes to our test environment tomorrow and are going to test there.

plush kelp
#

If you talk to our support team there may be a way for them to shut this off for you in test mode. As far as I am aware there isn't a way for you to do this yourself, but depending on how this was extended on our end it may be possible to shut it off in just one mode.

#

Also, the migrated VBANs shouldn't act any differently from customer balances originally created through the new API, so they should act properly even without any change like that on your account.

ancient wigeon
plush kelp