Zum Inhalt springen
NimbusNexus

Payment methods

Payment methods are the bank cards, ACH accounts, and (for enterprise) wire-transfer profiles attached to an account. One method is designated as the default — that's what gets charged on the monthly invoice. The others sit as fallbacks (we'll try them in order if the default fails).

Card data never touches NimbusNexus directly — payment-method creation routes through our PCI-compliant payment processor (Stripe today), and we store only the tokenized reference + display metadata (brand, last four, expiration). You don't need to worry about PCI scope on your end as long as you're using the API; raw card numbers never appear in any request to NimbusNexus.

What's next

Reference

POST/api/v1/payment/payment_methods/{payment_method_id}/add_funds

Add Funds

Charge a vaulted card to add wallet funds (top-up). A 'requires_action' result carries a client_secret the frontend 3DS-confirms, then re-syncs.

Parameters

NameInRequiredDescription
payment_method_idpathyes—
Idempotency-Keyheaderyes—

Request body

JSON body required.

Responses

  • 200Successful Response
  • 422Validation Error

https://api.nimbusnexus.net/api/v1/payment/payment_methods/{payment_method_id}/add_funds

Need to make a real call? Try these endpoints in the live Swagger UI →