-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add bncode to headers in orders api calls #6
Conversation
@@ -37,12 +38,14 @@ async function createOrder( | |||
payload: OrderPayload | |||
): Promise<CreateOrderResponse> { | |||
const basicAuth = btoa(`${getClientID()}`); | |||
const partnerAttributionId = getPartnerAttributionID(); | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We dont support Client Side Create Order right. I don't think we ask Merchants to use this at all. This method to CreateOrder
can actually be removed from the Component . We can add to just ApproveApplePayment
call
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't sure if this was being used as a placeholder for future use. If it were, we'd want to get the partnerAttributionId in this call.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, To give some background context. This was added as a plan to Support Client Side Create Order But it is being decided that we will no longer support Client Side Order Creation not just for ApplePay but across the board.
A Follow up PR would suffice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove the Client Side Create Order Util . We dont expose the clientSide code and all and we are moving to only ServerSide Order Creation anyways
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow Up Changes to Remove the Client Side Code
Merge after Build Passes |
https://paypal.atlassian.net/browse/DTALTPAY-1294
Add bncode (paypal-partner-attribution-id) header so orders API calls (CSPS/CBPS downstream) will receive bncode
With data-partner-attribution-id:
https://sh-pp-observability.us-central1.gcp.dev.paypalinc.com:8000/en-US/app/monitoring-splunk-app/log-vie[…]Amsmaster5int-g_checkoutbuyerplatserv_0
Without data-partner-attribution-id:
https://sh-pp-observability.us-central1.gcp.dev.paypalinc.com:8000/en-US/app/monitoring-splunk-app/log-vie[…]Amsmaster4int-g_checkoutbuyerplatserv_1
Dependent on corresponding xobuyer PR to pass this info to CBPS/CSPS