#yokogi_best-practices

1 messages · Page 1 of 1 (latest)

woeful spearBOT
#

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

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

spice elk
woeful spearBOT
hexed lodge
#

The following are the contents of the file.

Optimal Stripe Connect Configuration for 
  LIFF-based Multi-tenant Payment Platform

  System Architecture

  - Platform Type: Multi-tenant payment platform utilizing LINE LIFF (LINE
  Front-end Framework)
  - Account Structure:
    - Platform Account: Managed by our company
    - Connected Accounts: Held by each channel administrator
  - Tech Stack: Laravel 10 + Vue 3 + LINE LIFF

  Payment Flow

  1. Channel administrators place LIFF URL on their EC sites
  2. End users click the LIFF URL on the EC site
  3. Transition to our system (within LIFF) to input required information
  4. After clicking "Process Payment" button, redirect to Stripe Checkout
  5. End users complete payment on Stripe-hosted form
  6. Revenue goes to connected account (channel administrator), fees to
  platform

  Business Requirements

  1. Payment Types:
    - One-time payments (product purchases)
    - Subscription payments (recurring purchases)
    - Bank transfer support (Furikomi) desired
  2. Fee Structure:
    - Platform fee: 10% (planned)
    - Revenue distribution to each channel administrator

  Technical Constraints (Mandatory Requirements)

  1. PCI-DSS Non-compliance:
    - No handling of card information whatsoever
    - Stripe Checkout usage is mandatory
  2. Development Resources:
    - Want to avoid Custom account implementation
    - Prefer Stripe-hosted onboarding
    - Leverage existing Stripe Connect implementation

  Questions

  1. Are Express accounts available in Japan?
  2. What is the optimal Connect configuration for LIFF-based payment flow?
    - Express + Destination charges
    - Standard + Direct charges (OAuth required?)
    - Other options
  3. What are the constraints when implementing bank transfers (Furikomi) 
  with Checkout?
  4. What is the simplest way to implement channel administrator 
  onboarding?
  5. Are there any recommended best practices?
naive gulch
#

hello! fyi i'm taking over for my colleague here - fyi the server is a little busy atm so my response might be a little slow

hexed lodge
#

Noted. Please reply when you are available.

spice elk
#
  1. What is the optimal Connect configuration for LIFF-based payment flow?
#

THe main question is who you want to be responsible for refunds/disputes, the platform or the Connected Account? If it's the Platform, then you shoul duse Destination Charges, and if it's te Connected Account then you shoul Direct Direct Charges

#
  1. What are the constraints when implementing bank transfers (Furikomi)
    with Checkout?
    Sorry but this is a board question, could you be more specific ? if no, you could start doing some tests on Stripe test mode
    https://docs.stripe.com/testing
#

and share with us any issues you may be facing..

hexed lodge
# 
Thank you for your response.

I would like to confirm an additional point.
We are currently using platform account destination payments, but a customer who has asked us to modify the system has requested that we change the responsibility for refunds/disputes to a connected account. We are therefore considering direct payments for the Standard account.

I am aware of the following issues when using Direct Payments, is this correct?
1. when using direct payments, there must be an OAuth link between our system and Stripe, and if the link is broken, the end user will not be able to use the payment.
(2) Bank transfers with Stripe require a virtual account to be issued, and a virtual account cannot be issued for each consolidated account, so end-users cannot use bank transfers when using direct payments and checkout.
3. when using direct payments for Standard accounts, the risk of OAuth breakage can only be tolerated
woeful spearBOT
orchid shard
#

hi! I'm taking over this thread.

#

We are therefore considering direct payments for the Standard account.
if you want the connected account to handle refunds/disputes, then yen you have to use Direct Charges

#
  1. when using direct payments, there must be an OAuth link between our system and Stripe, and if the link is broken, the end user will not be able to use the payment.
    The platforms needs to be connected to the connected account for Direct Charges to work.
#

(2) Bank transfers with Stripe require a virtual account to be issued, and a virtual account cannot be issued for each consolidated account, so end-users cannot use bank transfers when using direct payments and checkout.
I'm not sure I understand, but yes you can use bank transfer with Direct Charges

#
  1. when using direct payments for Standard accounts, the risk of OAuth breakage can only be tolerated
    No idea what that means, sorry
hexed lodge
#

Thank you for your response.

I was aware of the following restrictions, so I am aware that I cannot use bank transfers using checkout for direct payments, is this a mistake?

  1. restrictions on issuing virtual accounts
    • Virtual account numbers are only issued to platforma
      accounts
    • Virtual accounts are not issued to consolidated accounts (regardless of Standard/Express
      )
  2. Direct payment mechanism
    • Payments are processed directly on the consolidated account
    • Even if a consolidated account activates bank transfers (custom
      er_balance), this is not possible due to the absence of the virtual account
orchid shard
#

I was aware of the following restrictions,
I'm not sure I understand these restrictions, but where are they coming from?

hexed lodge
#

Sorry, you may have misread the documentation.
I would like to reconfirm, am I correct in this understanding?
Virtual accounts can be issued for each consolidated account, so bank transfers using checkout can be used for direct payments.

However, the risk of using direct payments is that end-users will not be able to make payments if the OAuth link is removed from the Stripe dashboard, etc.

orchid shard
#

I would like to reconfirm, am I correct in this understanding?
I'm sorry but I don't understand what part exactly you want confirmation. If you are asking if bank transfer are supported with Connect, then then answer is yes: https://docs.stripe.com/payments/bank-transfers#connect

#

However, the risk of using direct payments is that end-users will not be able to make payments if the OAuth link is removed from the Stripe dashboard, etc.
If the connected account is disconnecte from the platform, then yes you won't be able to do Direct Charge. but I don't really understand why this would be an issue.

hexed lodge
#

I'm sorry but I don't understand what part exactly you want confirmation.
If we know that bank transfers are available for direct payment and checkout, it is not a problem, is that a final confirmation, is it correct that it is not a problem?

but I don't really understand why this would be an issue.
It is assumed that the holder of the consolidated account to be OAuth-linked and the end user who actually uses the checkout payment are different. Therefore, we are asking because we are concerned that end-users will not be able to make payments if the OAuth linkage is broken.

orchid shard
#

we are asking because we are concerned that end-users will not be able to make payments if the OAuth linkage is broken.
But why would you disconnect the connected account in the first place?

hexed lodge
#

I'm sorry but I struggle to understand what your question is. Did you read the documentation link I shared?
I have read the documentation and I am asking the question just to be sure.
If you can see that you can use bank transfer with direct payment and checkout, that is fine, thank you.
But why would you disconnect the connected account in the first place?
I am just concerned about the fear of an operational error, for example, that you might disconnect the link on the dashboard. Basically, I don't think it will be a problem.

orchid shard
#

I have read the documentation and I am asking the question just to be sure.
Which question?
I am just concerned about the fear of an operational error, for example, that you might disconnect the link on the dashboard. Basically, I don't think it will be a problem.
Well yes if the connected account is disconnected, the Direct Charge will fail as expected.

woeful spearBOT
robust harness
#

👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!

hexed lodge
#

Which question?
The question is whether end users can use bank transfers with Standard account and direct payment and checkout. We would like to check just to be sure.

robust harness
#

yes they can