--- title: "SmartBin" description: "A non-technical overview of SmartBin in RevCent, focused on how it helps route credit card payments to the gateway with the strongest statistical approval likelihood, how it depends on gateways and payment profiles, and how businesses should prepare, use, monitor, and understand SmartBin routing." type: "feature" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/feature/SmartBin.md" relationships: - name: "Gateway" url: "https://revcent.com/documentation/markdown/ecosystem/feature/Gateway.md" - name: "Gateway Group" url: "https://revcent.com/documentation/markdown/ecosystem/feature/GatewayGroup.md" - name: "Payment Profile" url: "https://revcent.com/documentation/markdown/ecosystem/feature/PaymentProfile.md" - name: "Customer Card" url: "https://revcent.com/documentation/markdown/ecosystem/item/CustomerCard.md" - name: "Transaction" url: "https://revcent.com/documentation/markdown/ecosystem/item/Transaction.md" technical_links: web_app: "https://kb.revcent.com/en/payments/credit-card/smartbin" api: sections: - name: "Gateways" section: "https://revcent.com/docs/api/v2#section-gateways" - name: "Payment Profiles" section: "https://revcent.com/docs/api/v2#section-payment_profiles" operations: - name: "Get User Gateways" operation_id: "GetUserGateways" operation: "https://revcent.com/docs/api/v2#operation-GetUserGateways" schema: "https://revcent.com/documentation/files/api/operation/GetUserGateways.json" - name: "Get A User Gateway" operation_id: "GetUserGateway" operation: "https://revcent.com/docs/api/v2#operation-GetUserGateway" schema: "https://revcent.com/documentation/files/api/operation/GetUserGateway.json" - name: "Edit A User Gateway" operation_id: "EditUserGateway" operation: "https://revcent.com/docs/api/v2#operation-EditUserGateway" schema: "https://revcent.com/documentation/files/api/operation/EditUserGateway.json" - name: "Get Payment Profiles" operation_id: "GetPaymentProfiles" operation: "https://revcent.com/docs/api/v2#operation-GetPaymentProfiles" schema: "https://revcent.com/documentation/files/api/operation/GetPaymentProfiles.json" - name: "Get A Payment Profile" operation_id: "GetPaymentProfile" operation: "https://revcent.com/docs/api/v2#operation-GetPaymentProfile" schema: "https://revcent.com/documentation/files/api/operation/GetPaymentProfile.json" mcp: related_markdown: - name: "Gateway Overview" markdown: "https://revcent.com/documentation/markdown/mcp/operation/OverviewGateway.md" - name: "Gateway Group Overview" markdown: "https://revcent.com/documentation/markdown/mcp/operation/OverviewGatewayGroup.md" - name: "Edit User Gateway" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditUserGateway.md" - name: "Create User Gateway" markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateUserGateway.md" --- # SmartBin SmartBin is a RevCent payment optimization feature that can help route a credit card payment request to the gateway with the strongest statistical likelihood of approval for that specific card and payment context. In the RevCent ecosystem, SmartBin should be understood as an advanced routing capability, not as a gateway, transaction, card record, or payment profile by itself. It works with configured Gateways, eligible Gateway Groups, Customer Card context, and Payment Profile gateway-selection logic. The practical idea is: ```text SmartBin = statistical gateway selection for a specific payment request ``` When SmartBin is active for a Payment Profile gateway choice, RevCent scores eligible gateways and uses that score to help choose the best available gateway for the payment. The purpose of this document is to explain the feature conceptually for LLMs, AI crawlers, and planning systems. It does not provide technical implementation instructions. For technical details, use the interface-specific links below. ## Technical Links by Interface | Interface | Use This When | Link | |---|---|---| | Web App | A human is learning about SmartBin setup, preparation, enablement, and monitoring. | [Web Knowledge Base](https://kb.revcent.com/en/payments/credit-card/smartbin) | | API | A developer is reviewing gateway metadata or related payment profile records used by SmartBin workflows. | [API Docs: Gateways](https://revcent.com/docs/api/v2#section-gateways) | | MCP / AI | An LLM, MCP client, or AI agent needs markdown-oriented gateway guidance that includes SmartBin requirements and caveats. | [MCP Markdown Overview: Gateway](https://revcent.com/documentation/markdown/mcp/operation/OverviewGateway.md) | --- ## Core Purpose The core purpose of SmartBin is to improve credit card approval strategy when a business has more than one usable gateway. Approval performance can vary by issuer, BIN, card brand, acquirer, processor, gateway, request type, and recent payment history. A static gateway order may not always choose the gateway most likely to approve a given customer card. SmartBin helps RevCent make a more informed gateway choice. Conceptually: ```text Payment request begins | Payment Profile reaches a Choose Gateway step | SmartBin evaluates eligible Gateways | Gateways receive request-specific SmartBin scores | The strongest eligible Gateway is selected | Transaction is attempted through that Gateway ``` SmartBin is most useful when gateway approval rates differ meaningfully across cards, issuers, brands, acquirers, or processors. --- ## Where SmartBin Fits in RevCent SmartBin sits inside RevCent's credit card routing layer. It connects to: - Gateways, because those are the configured payment destinations SmartBin can evaluate. - Gateway Groups, because a group may define the candidate gateway pool. - Payment Profiles, because SmartBin is used inside gateway-selection flow logic. - Customer Cards, because card details such as BIN and brand help shape the request-specific context. - Transactions, because Transactions record the actual payment attempts and outcomes after routing. SmartBin does not replace Payment Profiles. It helps a Payment Profile choose between eligible gateways when the profile is configured to use SmartBin for a gateway choice. --- ## Relationship to Gateways Gateways are the configured merchant gateway accounts, MIDs, or processor connections in RevCent. SmartBin depends on gateway context because it needs to compare possible payment destinations. Gateway setup may include SmartBin-related metadata such as card-brand-specific acquirer information, MID values, BIN values, MCC values, and processor context. Gateway-level SmartBin metadata is preparation data. It is not the same as activating SmartBin routing. The distinction is important: ```text Gateway SmartBin metadata = information that can help SmartBin scoring Account and Payment Profile SmartBin enablement = conditions required for SmartBin routing ``` A gateway can have SmartBin metadata configured and still not be selected through SmartBin if the account or Payment Profile is not configured to use SmartBin. --- ## Relationship to Gateway Groups Gateway Groups can define the candidate set SmartBin evaluates. If a Payment Profile Choose Gateway node uses a Gateway Group and SmartBin is enabled for that choice, SmartBin can score the eligible Gateways in that group. Conceptually: ```text Gateway Group | Eligible Gateways in the group | SmartBin scores those Gateways | Payment Profile chooses a Gateway from that candidate pool ``` Changing a Gateway Group used by a SmartBin-enabled Payment Profile can change which Gateways SmartBin is allowed to consider. For that reason, Gateway Groups used with SmartBin should be intentional and specific to the payment strategy. --- ## Relationship to Payment Profiles Payment Profiles are where SmartBin becomes operational. A Payment Profile can contain a Choose Gateway node. When SmartBin is enabled for that gateway choice, RevCent can evaluate the available gateways and order or choose them according to SmartBin scoring. The basic relationship is: ```text Payment Profile = routing flow Choose Gateway node = point where gateway candidates are selected SmartBin = scoring logic that can rank eligible candidates ``` SmartBin should not be described as a standalone switch that changes every payment in the account. It applies when the account has SmartBin enabled and the relevant Payment Profile choice is configured to use it. --- ## SmartBin Enablement Requirements SmartBin requires multiple pieces to be in place. At a conceptual level: 1. RevCent must enable SmartBin for the account. 2. The business should have more than one useful gateway candidate. 3. Gateway SmartBin and acquirer information should be prepared. 4. The relevant Payment Profile should use a Choose Gateway step. 5. SmartBin must be enabled for that gateway choice. If only the gateway metadata is configured, SmartBin routing may still not happen. If only one gateway is available, SmartBin has no meaningful choice to make. --- ## Gateway Preparation SmartBin works best when gateway and acquirer information is accurate. Preparation usually means reviewing all configured gateways, including dormant or historical gateways, and setting relevant acquirer details for each card brand when available. Historical data matters because SmartBin scoring depends on past payment outcomes and gateway context. Helpful gateway information may include: - Card-brand-specific acquirer. - Merchant account ID or MID. - Gateway BIN. - Merchant category code, often called MCC. - Processor. - Gateway purpose, brand, region, or routing role. This information should come from the business, processor, merchant account provider, or authoritative gateway records. AI and MCP workflows should not invent acquirer, processor, MID, BIN, or MCC values. --- ## SmartBin Scoring SmartBin scoring is request specific. RevCent evaluates historical payment behavior and current routing context to produce a score for eligible gateways. The exact scoring is more complex than a simple approval-rate sort. It may include historical outcomes, recent transaction patterns, issuer behavior, gateway context, time windows, anomalies, gateway volume, and other conditions. The important concept for crawlers and planning systems is: ```text SmartBin does not score a Gateway once forever. SmartBin scores eligible Gateways for the payment request being processed. ``` This helps avoid overloading one gateway for a specific issuer or card pattern and gives newer gateways limited opportunities for sampling when there is not enough historical data. --- ## When SmartBin Is Useful SmartBin is usually useful when: - The business uses multiple gateways. - Approval rates vary by issuer, BIN, card brand, acquirer, processor, or gateway. - The business wants to choose the gateway most likely to approve a specific payment request. - Gateway Groups are already organized around brand, region, product, or payment use case. - The Payment Profile can expose a sensible candidate pool for SmartBin to evaluate. - The business has enough historical transaction data to make scoring meaningful. SmartBin is part of payment optimization. It is most valuable for businesses that have real routing choices and measurable gateway performance differences. --- ## When SmartBin Is Not Useful SmartBin is usually not useful when: - The business only has one gateway. - The account is not enabled for SmartBin. - The Payment Profile does not use a SmartBin-enabled Choose Gateway node. - Gateway data is incomplete or inaccurate. - Gateway approval rates are already consistently high across available routes. - The business needs an explicit fixed gateway choice instead of statistical selection. SmartBin should not be treated as a replacement for clear payment strategy. It improves gateway choice only inside the eligible candidate set the business provides. --- ## When SmartBin May Not Be Used Even when SmartBin exists in an account, it may not determine the final gateway for every payment request. Examples include: - A Payment Profile does not reach a SmartBin-enabled Choose Gateway node. - Only one gateway remains eligible after prior routing logic. - Prefer-gateway logic creates a preferred gateway selection before SmartBin should apply. - Subscription or trial preference logic intentionally overrides normal gateway choice. - Gateway cascade rules, time rules, revenue rules, or enabled status remove one or more gateways from consideration. - The payment request is routed through a different Payment Profile path. In other words: ```text SmartBin can score eligible candidates. It does not guarantee that every configured Gateway is considered. ``` --- ## Monitoring SmartBin Results SmartBin should be monitored through actual payment outcomes. A business may review Transactions and payment flow details to see whether SmartBin was used, which gateways were considered, how the gateway order was produced, and how the resulting Transaction performed. Useful questions include: - Which Transactions used SmartBin? - Which Gateway was selected? - Which Gateways were available as candidates? - What SmartBin order or scoring information was visible? - Were approvals improving after SmartBin enablement? - Did any gateway receive too much or too little volume? - Are new gateways being sampled in a controlled way? - Are prefer-gateway rules preventing SmartBin from running? SmartBin should be evaluated over time. A single Transaction may not prove whether the strategy is working. --- ## Relationship to Transactions and Reporting Transactions record what happened after gateway selection. SmartBin influences gateway selection before the Transaction is attempted, but the Transaction item records the actual result: approval, decline, error, gateway, response details, and related payment context. Conceptually: ```text SmartBin influences Gateway selection | Payment Profile processes the payment | Transaction records the outcome | Reporting can compare SmartBin usage and gateway performance ``` SmartBin itself should not be treated as a standalone reporting table unless a specific reporting schema provides that data. In practice, SmartBin performance analysis usually depends on Transaction outcomes, gateway context, Payment Profile behavior, and payment flow details. --- ## Operational Safety SmartBin affects live payment routing. Incorrect setup may cause: - The wrong gateways to be available as candidates. - Important gateways to be missing from the candidate pool. - Gateways to be selected with incomplete metadata. - Prefer-gateway rules to override expected SmartBin behavior. - Gateway groups to include candidates that should not compete with each other. - Payment operations teams to misread why a gateway was selected. For this reason, SmartBin should be enabled intentionally, with clear gateway groups, accurate gateway metadata, and a known Payment Profile strategy. --- ## AI Assistant and MCP Guidance AI Assistants and MCP clients should treat SmartBin as an advanced payment-routing capability. Before describing a SmartBin setup as active, AI should confirm: - SmartBin is enabled for the RevCent account. - The relevant Payment Profile contains a SmartBin-enabled Choose Gateway node. - The candidate Gateways or Gateway Group are known. - Gateway SmartBin/acquirer information has been prepared. - Prefer-gateway logic and cascade rules have been considered. - The business understands this can affect live credit card routing. AI and MCP workflows should not: - claim that gateway metadata alone activates SmartBin; - invent acquirer, MID, BIN, MCC, processor, or gateway values; - assume SmartBin is useful when there is only one gateway; - imply that every payment will use SmartBin; - change payment-routing behavior without explicit business intent. --- ## Common Misunderstandings ### "SmartBin is a gateway." No. SmartBin is a gateway-selection capability. Gateways are the configured payment destinations. ### "Adding SmartBin metadata to a Gateway activates SmartBin." No. Gateway metadata prepares the gateway for better scoring context, but account-level enablement and Payment Profile configuration are also required. ### "SmartBin always chooses from every gateway in the account." No. SmartBin scores eligible gateways in the candidate set exposed by the Payment Profile and related routing rules. ### "SmartBin replaces Payment Profiles." No. SmartBin works inside Payment Profile gateway-selection logic. ### "SmartBin is helpful with one gateway." Usually no. SmartBin is designed for situations where there are multiple possible gateways to compare. --- ## Best-Fit Businesses SmartBin is best suited for ecommerce businesses that: - process meaningful credit card volume; - use multiple gateways or merchant accounts; - see approval performance vary by issuer, BIN, brand, gateway, or acquirer; - maintain clear Gateway Groups and Payment Profiles; - want to improve authorization strategy with statistical gateway selection; - can monitor approval, decline, chargeback, and gateway-volume results over time. It is usually unnecessary for businesses with a single gateway, simple routing, or no meaningful approval-rate variation. --- ## Summary SmartBin is RevCent's advanced gateway-selection capability for routing credit card payments toward the gateway with the strongest statistical approval likelihood for a specific payment request. The key concept is: ```text Gateway and Gateway Group = possible payment destinations Payment Profile = routing flow that exposes the candidate set SmartBin = statistical scoring for eligible gateway candidates Transaction = actual payment attempt and outcome ``` Used well, SmartBin can help ecommerce businesses improve approval strategy across multiple gateways. It should be prepared carefully, enabled intentionally, monitored through Transactions and payment flow details, and understood as part of the broader Payment Profile routing system. --- Document Parent Directory * [Features](https://revcent.com/documentation/markdown/ecosystem/feature/index.md) - Non-technical markdown documentation for features within the RevCent ecosystem. A feature is a part of the RevCent ecosystem that a user can create and configure.