# Take payments

> Connect your processor. Card numbers never touch your site or ours.

Source: https://docs.dashfordevs.com/v1/analytics-and-money/payments · Topic: Analytics, payments and finance · Updated: 2026-11-07

## Connect your processor

1.  Open **Organization → Integrations → Payments**.
    
2.  Add your processor account (for example Authorize.net). Start with its **sandbox** keys to test, then switch to live.
    
3.  Run a test order on your site. When it works, switch the connection to live.
    

Your processor credentials are encrypted and only ever shown masked (the last four characters).

## What we never store, and never send

-   **No card numbers.** The card is turned into a one-time token inside the shopper's browser by the processor's own script. We keep only the processor's ids, the card brand, the last four digits and the expiry.
-   **No product names to the processor.** The processor sees "Item 1, Item 2" and an order number, never what was bought. For a health store, that keeps purchases private even from the payment company.

## Subscriptions and refunds

Subscriptions renew automatically on their schedule. Refunds are made from the order page and sent to the processor.

**Not to be confused with your plan.** These are your customers paying you. What you pay DashForDevs is under [Your plan and invoices](https://docs.dashfordevs.com/v1/analytics-and-money/your-plan-and-invoices).