Skip to main content

Built-in Card Acquiring

Built-in card acquiring connects TrexWallet payment orders to Stripe Checkout and T-Bank Acquiring. TrexWallet owns the order, tariff, and final payment status. The card integration creates provider sessions, verifies provider callbacks, and reconciles pending payments.

When It Is Used​

Card FlowProcessing
Built-in Stripe CheckoutBuilt-in card acquiring
Built-in T-Bank AcquiringBuilt-in card acquiring
Custom card acquirerMerchant continuation flow

Custom card acquirers use a merchant continuation flow configured on the terminal.

Payment sequence​

  1. The payer selects a built-in card terminal on /pay.
  2. TrexWallet locks the order to that terminal and applies the tariff.
  3. The card integration creates a provider checkout session.
  4. The payer completes checkout on the provider side.
  5. The provider sends a callback, or reconciliation obtains the final status.
  6. TrexWallet marks the payment confirmed, failed, canceled, or timed out.

Reconciliation​

Provider callbacks are best-effort. Reconciliation checks pending provider sessions and updates TrexWallet when the provider reaches a terminal status.

Configuration​

Operators configure:

  • the private service endpoint and deployment-issued service credentials;
  • provider credentials;
  • provider webhook secrets;
  • optional provider callback URL when the provider requires it.

Keep provider secrets in deployment configuration and rotate them in the provider portal when needed.

Operator Setup​

  1. In /TrexAdmin/TokenNetworks, create or enable a built-in acquiring terminal.
  2. Set the terminal contract to card acquiring and allow payment orders.
  3. Leave flow path empty so /pay uses the built-in card widget.
  4. Configure the matching tariff in /TrexAdmin/Tariffs.
  5. Configure provider credentials in deployment settings.
  6. Test a small card payment and verify it appears in /TrexAdmin/GatewayOrders.

Routing​

The payment page uses the standard public payment routes. Provider callbacks use the reserved acquiring callback route and are verified with provider signatures. Merchant continuation flows must not use the acquiring callback prefix.

Operational Notes​

  • Provider network errors are logged and covered by reconciliation.
  • Provider secrets stay in protected deployment settings.
  • If built-in card acquiring is disabled, card checkout becomes unavailable; crypto, internal payments, and merchant continuation keep working.

See Also​