This repository has been archived by the owner on Feb 27, 2023. It is now read-only.
Add order_id to Charges and my_customer_id to Customers created in sample app.
#35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n sample app. This shows off using the `metadata` field to include application-specific information in the Stripe objects. These metadata fields can be used for looking up the associated Order/Customer in your app's backend, given the Order/Customer from Stripe.
|
Tested by curling each endpoint, with & without additional Also quickly ran through the standard + custom iOS apps to make sure they weren't broken. |
danj-stripe
added a commit
to stripe/stripe-ios
that referenced
this pull request
Aug 7, 2018
…ios-backend` The value is meaningless, it's just a randomly generated UUID `B3E611D1-5FA1-4410-9CEC-00958A5126CB`. However, along with the changes from stripe/example-mobile-backend#35, this shows off some of what `metadata` can be used for. I am *not* adding metadata to each location where the Stripe API is directly used, only the places that go through stripe/example-ios-backend. Many of the places that directly deal with the stripe-ios SDK could *also* add metadata. That's being omitted for simplicity. See also IOS-356
danj-stripe
added a commit
to stripe/stripe-ios
that referenced
this pull request
Aug 8, 2018
…ios-backend` (#1008) * Add client-side metadata `charge_request_id` to requests to `example-ios-backend` The value is meaningless, it's just a randomly generated UUID `B3E611D1-5FA1-4410-9CEC-00958A5126CB`. However, along with the changes from stripe/example-mobile-backend#35, this shows off some of what `metadata` can be used for. I am *not* adding metadata to each location where the Stripe API is directly used, only the places that go through stripe/example-ios-backend. Many of the places that directly deal with the stripe-ios SDK could *also* add metadata. That's being omitted for simplicity. See also IOS-356 * Update links to example-ios-backend to use v13.2.0 tag
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This shows off using the
metadatafield to include application-specific informationin the Stripe objects.
These metadata fields can be used for looking up the associated Order/Customer in your
app's backend, given the Order/Customer from Stripe.