QuorumWiki
Jugar

Proveedor de pagos

Cobra las tarjetas en cada checkout. 2.9% más $0.30 por checkout.

Esta página aún no está traducida al español.

The Payment Provider stands for Stripe: the third party that charges your customers' cards.

When to place it#

  • Place it when you ship the Checkout Feature. Without it, checkouts have nowhere to charge.

  • Resize it before a spike, because past its tier's rate it drops charges.

It unlocks with the Checkout Research.

How it works#

Link an App Server to it, and each checkout sends one charge. It is a Managed Component, so it costs nothing to place, serves every region, and takes a fee from each successful checkout. Each charge waits a long, fixed time, which shows in the Checkout p99. Each size step is a usage tier that doubles how many charges per second it takes.

Do not confuse it with Payments, the drawer where your revenue waits. Checkouts are the highest-value request kind, so the Payment Provider sits on your most important path.

Options#

ControlValoresCuándo
ProveedorPrimer proveedor / Segundo proveedorSiempre
  • Provider: the first provider takes every checkout. The second serves while the first is down, and charges more per checkout. Set it before an outage, or press Switch provider when one starts.

How it fails#

  • Past its tier's rate, it drops charges. Resize it before a spike.

Payment provider outage#

  • Signs: Its Inspector reads "Their outage, not yours. Every checkout fails." and buy fails as upstream.

  • Do now: Press Switch provider. It costs Cash, and the second provider keeps serving at once. Nothing else ends it before its run of at most 60 s.

  • Prevent: Set the Provider to Second before an outage. The second provider charges more per checkout. No Research prevents the outage itself.

Double charge#

  • Signs: Charges slow down, duplicate errors appear, and refunds follow.

  • Do now: Set the charge Link's retries to No retries in the App Server's Calls section. With no retrying Link into the provider, the incident ends.

  • Prevent: Research Idempotency keys and do the Idempotency keys task. Do not turn on retries on the charge Link before then. See idempotency.

Flash sale#

  • Signs: E-commerce only. buy demand runs at ×20 for minutes, and the Database and the Payment Provider saturate.

  • Do now: Resize the Payment Provider up, because its tier sets how many charges it takes. Nothing else adds capacity here.

  • Prevent: Put a Queue in front of the checkout work, and research Autoscaling and Priority load shedding.

Instance failure#

  • Signs: The Payment Provider's card goes grey, its Inspector reads "The host under this VM died. It still bills.", and the requests sent to it are stranded.

  • Do now: Press Replace in its Inspector and pay the price. It comes back cold.

  • Prevent: Place a second Payment Provider, so it no longer stands alone.

Tips#

  • Do not turn on retries on the charge link until you own Idempotency keys.

  • Give the charge link a timeout longer than a normal charge.

Reglas#

  • Cada copia adicional cuesta un 25% más que la anterior.
  • Al venderlo se devuelve el 50% de lo que costó su última copia.
  • Tiene 8 tamaños. Cada paso duplica su capacidad y su Gasto.

Funciona con#

Pagos, Cola

Investigación siguiente#

Cuando tengas Checkout, estas Investigaciones se apoyan en ella.

Claves de idempotencia

Términos de ingeniería#