Connector Improvement: [Stripe] Add the missing `payment_method` element and missing `payment_method_details` object from the `charge` endpoint response
CompletedHi Fivetran,
The current schema generated for the denormalization of the `charge` object from Stripe's Charges API is missing the element `payment_method` and the nested object `payment_method_details` that contain relevant information from the captured payment.
Stripes charge object docs: https://stripe.com/docs/api/charges/object, the current JSON of the charge object below with `payment_method` and `payment_method_details` in bold. CVC and address checks are quite relevant for us, as well as the 3DS state.
Would it be possible to add these two with denormalization to the current charge schema? What's your best guesstimate to add these?
{
"id": "ch_3LGIxR2eZvKYlo2C1cv0wi18",
"object": "charge",
"amount": 100,
"amount_captured": 0,
"amount_refunded": 0,
"application": null,
"application_fee": null,
"application_fee_amount": null,
"balance_transaction": "txn_1032HU2eZvKYlo2CEPtcnUvl",
"billing_details": {
"address": {
"city": null,
"country": null,
"line1": null,
"line2": null,
"postal_code": null,
"state": null
},
"email": null,
"name": "Jenny Rosen",
"phone": null
},
"calculated_statement_descriptor": null,
"captured": false,
"created": 1656578561,
"currency": "usd",
"customer": null,
"description": "My First Test Charge (created for API docs)",
"disputed": false,
"failure_balance_transaction": null,
"failure_code": null,
"failure_message": null,
"fraud_details": {},
"invoice": null,
"livemode": false,
"metadata": {},
"on_behalf_of": null,
"outcome": null,
"paid": true,
"payment_intent": null,
"payment_method": "card_19yUNL2eZvKYlo2CNGsN6EWH",
"payment_method_details": {
"card": {
"brand": "visa",
"checks": {
"address_line1_check": null,
"address_postal_code_check": null,
"cvc_check": "unchecked"
},
"country": "US",
"exp_month": 12,
"exp_year": 2020,
"fingerprint": "Xt5EWLLDS7FJjR1c",
"funding": "credit",
"installments": null,
"last4": "4242",
"mandate": null,
"moto": null,
"network": "visa",
"three_d_secure": null,
"wallet": null
},
"type": "card"
},
"receipt_email": null,
"receipt_number": null,
"receipt_url": "https://pay.stripe.com/receipts/acct_1032D82eZvKYlo2C/ch_3LGIxR2eZvKYlo2C1cv0wi18/rcpt_LyFSl80zY48uvRf24eCccWFDTS9W9J4",
"redaction": null,
"refunded": false,
"refunds": {
"object": "list",
"data": [],
"has_more": false,
"url": "/v1/charges/ch_3LGIxR2eZvKYlo2C1cv0wi18/refunds"
},
"review": null,
"shipping": null,
"source_transfer": null,
"statement_descriptor": null,
"statement_descriptor_suffix": null,
"status": "succeeded",
"transfer_data": null,
"transfer_group": null
}
Best,
Julio
-
Official comment
Hi all,
We land the full payment_method_details object from Stripe's Charge response in the charge_payment_method_details table, keyed by charge_id and payment_method_type.
Best,
Sadie Martin, Product Manager
-
Hi Julio - Thanks for submitting this feature request. There is actually a similar feature request here for the same object to be added. We are aware of this objects need in our schema and right now this is on our backlog to be added in an upcoming phase of work.
Best,
Erin -
Hello, I was wondering if you had any updates on this? The data in this object would be very useful for our data warehouse as it contains things like zip_check and cvc_check values. I am currently blocked on doing risk analysis due to a lack of this data.
Please sign in to leave a comment.
Comments
3 comments