- https://merchant.bolt.com/ not working
- sandbox: https://api-sandbox.bolt.com
- production: https://api.bolt.com
onboard merchants
Page: 16 Check Platform Auth Credentials API
phone_authentication.last_four_digits // is this the last four digit of phone?
POST /v1/merchant/shopper_login lets a merchant sign a shopper into Bolt. If the shopper doesn’t exist, Bolt creates the account automatically.
doesnt that make Create New Bolt Account endpoint not required at all?
- caching the session token in response header for user
Page: 15 (only explains about passing them the stripe keys with data mapping and nothing else)
- Check Platform Auth Credentials API 'https://api-staging.bolt.com/v1/auth/check_platform_credentials'
- how do we know which credit card Tabbed user is registered under bolt?
- is it just using email as the bolt identifier? (is there external reference we can store from bolt?)
- connect.bolt.com/embed.module.js is web based
- using existing components instead of calling stripe, we call bolt based on feature flag
- tokenize new cards with Bolt.helpers.tokenize (page 44)
- find a webview library that can support bolt
- use expo-secure-store library on Tabbed app to store tokens
Set up payment processing (authorization, charging, refunds) that routes based on which provider the card is with (big chunk in core)
- libs/platform/src/common/payment-provider/bolt.service.ts
- mark user credit card as bolt payment provider
- preauth transaction for bolt
POST /v3/payments(page 23) - is finalizing a payment required
POST /v3/payments/{id}before capture payment/v1/merchant/transactions/capture? - is there a capture immediate option for payments?
- use
seller_splitsandseller_idto transfer to Tabbed merchant the portion and charged fees - if no
seller_splitsis defined in the sent payment, does it assume 100% split to Tabbed merchant
- Create feature flag
ACTIVE_PAYMENT_PROVIDER