Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add support for cost based debit routing #7543

Open
ShankarSinghC opened this issue Mar 18, 2025 · 0 comments · May be fixed by #7542
Open

add support for cost based debit routing #7543

ShankarSinghC opened this issue Mar 18, 2025 · 0 comments · May be fixed by #7542
Assignees
Labels
A-core Area: Core flows A-routing Area: Routing C-feature Category: Feature request or enhancement M-configuration-changes Metadata: This PR involves configuration changes

Comments

@ShankarSinghC
Copy link
Contributor

For every payment that occurs, there are three fees associated with the network:

  1. Network Fee
    Every network has its own network fee structure, which typically includes both a percentage (% of the amount) and a fixed fee. For each payment, the respective network will charge a specific percentage and a fixed amount.

  2. Interchange Fee
    If the bank is a regulated bank, it can charge only a specified percentage and fixed amount for the transaction. If the bank is not a regulated bank, then, similar to the network fee, the bank can charge different amounts depending on the network.

  3. Fraud Check Fee
    When a bank is regulated under an exemption for fraud checks, it may charge an additional fee only if a fraud check is conducted.

When a payment is being performed all this factors should be taken in consideration and a network should be chosen according to merchant's configuration

@ShankarSinghC ShankarSinghC added A-core Area: Core flows A-routing Area: Routing C-feature Category: Feature request or enhancement M-configuration-changes Metadata: This PR involves configuration changes labels Mar 18, 2025
@ShankarSinghC ShankarSinghC self-assigned this Mar 18, 2025
@ShankarSinghC ShankarSinghC linked a pull request Mar 18, 2025 that will close this issue
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-core Area: Core flows A-routing Area: Routing C-feature Category: Feature request or enhancement M-configuration-changes Metadata: This PR involves configuration changes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant