configure_credentials
Configure SATIM payment gateway credentials
LABSCO SUMMARY
Covers the awkward half of a payment, after the shopper leaves the page
Registration is the easy part; what usually breaks is deciding whether a returning shopper paid. confirm_order asks the gateway by orderId and validate_payment_response turns the raw response into a status, so the verdict does not rest on a redirect parameter. Refunds sit in the same tool set, which means a support conversation can end in a refund rather than a handover. Credentials can arrive through configure_credentials at runtime, so the environment variables are not the only route in.
What it is
A SATIM payment gateway client covering the order lifecycle: credential setup, order registration, post-payment confirmation, refunds and response interpretation.
What you get
- Order registration carrying orderNumber, amountInDA, currency, description, language and the returnUrl and failUrl the shopper is redirected to
- Order confirmation by orderId after a payment attempt, so the outcome comes from the gateway rather than from the redirect
- Refunds against a completed order for a stated amount and currency
- Interpretation of a raw gateway response into a payment status verdict
- Runtime credential configuration through configure_credentials, which takes userName and password directly
- Merchant-defined fields udf1 through udf5 on the registered order, plus force_terminal_id for routing
Requirements
A SATIM merchant account, three environment variables — SATIM_USERNAME, SATIM_PASSWORD and NODE_ENV — and GPL-3.0 terms if you redistribute the server.
Setup effort
Add the configuration to your client
USE CASES
01
Taking a first payment through SATIM without hand-rolling the redirect
The order is registered with its amount, currency and the two URLs the shopper comes back to, so the checkout hand-off is built from the gateway's own response.
02
Working out whether a shopper who came back actually paid
A redirect parameter is not proof of payment. The gateway is asked directly by orderId, and the raw response is turned into a status you can act on.
03
Refunding a customer during the support conversation
A refund against a completed order is issued from the same tool set that took the payment, so the exchange ends in an action rather than a handover.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
confirm_order
Confirm order status after payment attempt
refund_order
Process refund for a completed order
register_order
Register a new order with SATIM payment gateway
validate_payment_response
Validate and interpret payment response status
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. configure_credentials sets the merchant login at runtime, alongside SATIM_USERNAME and SATIM_PASSWORD in the config; which one takes precedence is not documented.
Requires
- npx on PATH
- Node.js 18+
- SATIM_USERNAME in your environment
- SATIM_PASSWORD in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"satim-payment": {
"command": "npx",
"args": [
"@devqxi/satim-payment-gateway-mcp"
],
"env": {
"SATIM_USERNAME": "<YOUR_SATIM_USERNAME>",
"SATIM_PASSWORD": "<YOUR_SATIM_PASSWORD>",
"NODE_ENV": "development"
}
}
}
}
