Read the card entry configuration

post

https://apis.kentro.live/store/v1/payments.cardConfig

For a store on Authorize.net: the public Accept.js configuration (provider: "authorize-net", apiLoginId, clientKey, sandbox) your page uses to tokenize a card into opaqueData for payments.save or checkout.start. For a store on NMI: the public Collect.js configuration (provider: "nmi", tokenizationKey, sandbox, scriptUrl) your page uses to tokenize a card into nmiPaymentToken for checkout.start. On any other store the answer is 503 UNAVAILABLE; a Stripe store saves cards on the hosted page payments.save answers. The body is empty.

Who may call it: A signed-in buyer (X-Storefront-Buyer); without one the answer is 401 UNAUTHORIZED.

Headers

X-Storefront-Host

string

required

length between 1 and 253

The published storefront host the request serves (shop.example.com, lower case). It must belong to the tenant of the API key; 404 NOT_FOUND when no published storefront answers it, 403 FORBIDDEN when it belongs to another account.

X-Storefront-Buyer

string

The signed-in buyer's access token (accessToken from POST https://apis.kentro.live/auth/login/customer). Absent for a guest or an anonymous visitor.

X-Storefront-Guest

string

The guest token session.guest answered, which identifies a guest cart and a guest checkout. Send it along with X-Storefront-Buyer at sign-in so the buyer can choose between the guest cart and the account cart.

X-Storefront-Client-Ip

string

The end buyer's IP address as your storefront server saw it. Used for per-visitor limits (search typeahead, sign-up); without it the limits apply to your server.

X-Expected-Portal

string

The store id (store.get answers id) your page was rendered for. When the host now resolves to another store the answer is 409 CONFLICT, so a stale page never acts on the wrong store.

X-Expected-Buyer

string

The identity your page was rendered for: the buyer id, guest:<guestId> for a guest, or guest for an anonymous visitor. A mismatch with the tokens sent is 409 CONFLICT, so a stale page never acts for the wrong buyer.

Responses

Language

Credentials

Header

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200The Accept.js or Collect.js configuration.

defaultThe request was refused or could not be completed; the status says why (400 validation, 401 sign-in needed, 403 not allowed, 404 unknown, 409 stale revision or version, 422 commerce rule, 429 too many, 503 unavailable).