## How it works

Organize your client around payment, customer, refund, dispute, product and subscription resources. Each operation corresponds to an HTTP request.

## Implementation

Create a small transport layer for the API host, authentication, JSON parsing and redacted diagnostics. Keep business IDs with your own records and preserve fields you do not yet consume. Follow the API reference for route-specific request fields; do not invent SDK method names. Use server retrieval to reconcile asynchronous payment updates.

## In this area

- Reconcile a payment
- Types
- Routes without a method

## Related guides

- [Dashboard API](/docs/sdks/rust/dashboard-api/overview/)
- [API reference](/docs/payment-api/reference/)
- [Accept payments](/docs/payment-api/accept-payments/)
- [Hosted checkout](/docs/payment-api/hosted-checkout/)
- [Refunds](/docs/payment-api/refunds/)